Bluesky relay software supports Sync v1.1, old firehose message types removed

What changed

On May 2, 2025 the AT Protocol team released an updated relay that supports Sync v1.1, is non-archival, adds a #sync message and a com.atproto.sync.listHosts endpoint, and removes #handle, #migration and #tombstone. Two new production relays, relay1.us-west.bsky.network and relay1.us-east.bsky.network, were made available. Moving bsky.network to the new relay was described only as coming in the near future.

What it means

Firehose consumers must stop relying on #handle, #migration and #tombstone, and expect higher sequence numbers after bsky.network switches.

Who is affected

Firehose consumers, PDS operators and relay operators on the AT Protocol.

What to do

Handle #identity and #account instead of the removed message types. PDS operators should test against the new relays and upgrade to emit valid Sync v1.1 messages before strict validation is enforced. No date is given for enforcement.