I’m having a problem with the FDSN Server. This morning I was getting 502 Bad gateway errors, but ATM it is reporting no FDSN service detected.
%runfile D:/Documents/Python/QR14any.py --wdir
Reloaded modules: importlib._common, importlib.resources, multiprocessing.dummy.connection, multiprocessing.dummy, http.cookiejar, http.cookies, encodings.cp437, fileinput, secrets
---------------------------------------------------------------------------
FDSNNoServiceException Traceback (most recent call last)
File d:\documents\python\qr14any.py:13
11 import cartopy.crs as ccrs
12 import cartopy.feature as cfeature
---> 13 rs = Client('https://data.raspberryshake.org/')
15 # Pretty paired colors. Reorder to have saturated colors first and remove
16 # some colors at the end. This cmap is compatible with obspy taup
17 cmap = plt.get_cmap('Paired', lut=12)
File ~\ObCa\lib\site-packages\obspy\clients\fdsn\client.py:277, in Client.__init__(self, base_url, major_versions, user, password, user_agent, debug, timeout, service_mappings, force_redirect, eida_token, _discover_services)
274 print("Request Headers: %s" % str(self.request_headers))
276 if _discover_services:
--> 277 self._discover_services()
278 else:
279 self.services = DEFAULT_SERVICES
File ~\ObCa\lib\site-packages\obspy\clients\fdsn\client.py:1650, in Client._discover_services(self)
1645 raise FDSNRedirectException(", ".join(redirect_messages))
1647 msg = ("No FDSN services could be discovered at '%s'. This could "
1648 "be due to a temporary service outage or an invalid FDSN "
1649 "service address." % self.base_url)
-> 1650 raise FDSNNoServiceException(msg)
1651 # Cache.
1652 if self.debug is True:
FDSNNoServiceException: No FDSN services could be discovered at 'https://data.raspberryshake.org'. This could be due to a temporary service outage or an invalid FDSN service address.
Also this morning the Raspberry Shake FDSN Web Service - DataSelect URL Builder is unresponsive.
Our team is aware of the issue and is actively working to address it.
The service is currently intermittently working, with no data being lost. I’ll update again when the team has more news or when the issue has been fixed.
Thank you for your notifications and your understanding.
There is no alternative way to my knowledge, but, in any case, I passed your request to our team, and they’ll see what can be done after the current FDSNWS access situation has been resolved.
To summarize, the data access issues only affect recent EHZ data (from Nov.1st onwards), that is why it was missing from your query (which included only EHE and EHN channels). While it is temporarily not retrievable, no data is being lost.
