The EarthScope-operated NSF National Geophysical Facility’s SeedLink streaming service, providing access to real-time streams from seismological networks, is moving from rtserve.iris.washington.edu to rtserve.earthscope.org as part of our cloud transition.
What: Transition of SeedLink service to a new address
When: June 8, 2026
Both services are now running in parallel for a transition period of approximately one month. We encourage all users to switch to rtserve.earthscope.org at their earliest convenience. On June 8, 2026, the DNS for rtserve.iris.washington.edu will be redirected to the new service, at which point any remaining client connections will be dropped and forced to reconnect to the new service.
We've worked to make this transition as smooth as possible, but if you encounter issues please contact he...@earthscope.org.
Action required: switch your client and discard saved connection state
When you reconfigure your SeedLink client to connect to rtserve.earthscope.org, discard any saved state file used to resume connections. The new service is an independent implementation and does not share state with the legacy server. Reusing legacy state can cause re-downloading large amounts of duplicate data already received.
The recommended procedure:
Stop your client.
Update the server address to rtserve.earthscope.org.
Delete or rename the existing SeedLink statefile.
Restart your client; it will begin acquiring data from the new service from the current time.
It is possible that this transition procedure will result in data gaps in some streams, with more gaps expected the longer the switch takes. If you wish to fill these data gaps, miniSEED can be requested from our fdsnws-dataselect service: https://service.earthscope.org/fdsnws/dataselect/1/
Forced cutover
On the cutover date, the DNS record for rtserve.iris.washington.edu will be updated to resolve to rtserve.earthscope.org. Existing connections to the old address will be dropped at that time, and clients will reconnect to the new service. Because server state cannot be preserved across this cutover, users who have not already migrated should expect a small gap or some data overlap when their client reconnects. Controlling this state transition is the primary reason we recommend migrating ahead of the forced cutover.
We will update this news item and send a follow-up email to the data-announcements list when the cutover has occurred.
What's new in the service
The new service brings several improvements:
