Hello,
It seems there have been issues with the timeliness of the FDSNWS service for some time now. Even now (9:08 UTC), the link to a recent earthquake in my neighborhood is blank.
https://data.raspberryshake.org/fdsnws/dataselect/1/query?starttime=2026-05-07T04:45:53&endtime=2026-05-07T04:48:53&network=AM&station=R28DF
It is of no use to me if data is filled in retroactively.
Can anything be done to change this situation?
Best regards
Hello jheiler, thanks for your notification.
I’ve asked the server team to check our FDSNWS logs (to see if we could identify the data retrieval issue there), and your request appears about 5 minutes before your message, with it being successfully satisfied as far as we can see.
Could you provide more details about what you saw when you ran the query so we can try to pinpoint and recreate the issue on our side? Was it from StationView, or a direct request from our FDSNWS portal?
Did you get a blank page, an empty MSEED file, or a permanently loading window? Or something different?
Testing it now, it appears that data is queried and retrieved correctly, but I understand it’s many hours after your first try. Thank you.
As general information for all readers who may be interested in this, the background server infrastructure has been updated (and constantly continues to be) with a definite improvement in performance. Not being a real-time streaming protocol, FDSNWS will serve data T-30 minutes and older.
Thank you.
I downloaded the data from the StationView website (“Event Data (MSeed format)”), but the MSeed file was empty.
Thank you, this is very helpful as it is a peculiar situation. I have passed this information to our server team.
If you haven’t already tried, could you:
Do you still get an empty MSEED, or is the file correctly filled?
works.
works except Channel: ENE.
Thank you, jheiler.
We are investigating the possible causes of the issue you’re seeing, and we’ll update you as soon as possible.
Hello again jheiler,
Our server team has completed their review and found that all data was present for the queries you’ve made (no data loss is always good news).
Therefore, it must have been a temporary glitch in the FDSNWS system that we were unable to reproduce (albeit a very unusual one, particularly with a single channel empty). If it happens again, could you attach the incomplete (or even the empty) MSEED file you downloaded so we can use it in our verifications?
Thank you again for your notifications about such events.
By pure chance, a similar situation happened to me yesterday, with a fully downloaded MSEED file containing all channels (verified via ObsPy).
However, when I opened it with SWARM, one channel was blank/missing and displayed no content, even though I knew it was there.
Thus, if something similar to what has been described in this topic happens again to anyone who reads, we now know that SWARM does not always display all channels in a miniseed file. We recommend closing and reopening SWARM, as that seems to resolve the issue.