Showing observation from: 2026-09-29 18:00:02 UTC (3600s)
| Host | API 1 | Run by | Location | Users | Events | % of max 2 | Uptime 3 |
|---|---|---|---|---|---|---|---|
| sfo.firehose.stream | @sri.xyz | 🇺🇸 Oregon (OVH) | 209,199 | 1,648,341 | 100.00% | 100.0% | |
| relay.bas.sh | @bas.sh | 🇩🇪 Germany (Hetzner) | 208,979 | 1,530,977 | 99.89% | 100.0% | |
| asia.firehose.network | @sri.xyz | 🇮🇳 Mumbai (OVH) | 208,921 | 1,528,052 | 99.87% | 100.0% | |
| nyc.firehose.stream | @sri.xyz | 🇺🇸 Virginia (OVH) | 208,918 | 1,645,917 | 99.87% | 100.0% | |
| chennai.firehose.stream | @sri.xyz | 🇮🇳 Mumbai (OVH) | 208,909 | 1,685,007 | 99.86% | 100.0% | |
| relay1.eurosky.network | Eurosky | 🇩🇪 Germany (Hetzner) | 208,754 | 1,527,137 | 99.79% | 100.0% | |
| jetstream2.fr.hose.cam | @bad-example.com | 🇩🇪 Germany (Hetzner) | 208,752 | 1,683,399 | 99.79% | 100.0% | |
| relay3.fr.hose.cam | @bad-example.com | 🇫🇷 France (OVH) | 208,744 | 1,526,243 | 99.78% | 100.0% | |
| relay1.us-east.bsky.network | Bluesky PBC | 🇺🇸 Virginia (–) | 208,741 | 1,527,216 | 99.78% | 99.4% | |
| jetstream1.eurosky.network | Eurosky | 🇩🇪 Germany (Hetzner) | 208,737 | 1,684,150 | 99.78% | 100.0% | |
| bsky.network | Bluesky PBC | 🇺🇸 California (–) | 208,726 | 1,527,602 | 99.77% | 100.0% | |
| relay1.us-west.bsky.network | Bluesky PBC | 🇺🇸 California (–) | 208,726 | 1,527,602 | 99.77% | 100.0% | |
| relay.fire.hose.cam | @bad-example.com | 🇨🇦 Montreal (ServaRica) | 208,709 | 1,529,469 | 99.77% | 100.0% | |
| atproto.africa | Blacksky Algorithms | 🇺🇸 Virginia (OVH) | 208,520 | 1,524,045 | 99.68% | 95.3% | |
| jetstream.us-west.bsky.network | 2 | Bluesky PBC | 🇺🇸 California (–) | 208,504 | 1,641,424 | 99.67% | 100.0% |
| jetstream.us-east.bsky.network | 2 | Bluesky PBC | 🇺🇸 Virginia (–) | 208,503 | 1,641,388 | 99.67% | 99.4% |
| relay.t4tlabs.net | @isla.pet | 🇨🇦 Toronto (Xenyth) | 207,546 | 1,500,893 | 99.21% | 100.0% | |
| jetstream1.us-east.fire.hose.cam | @bad-example.com | 🇺🇸 Virginia (Hetzner) | 207,537 | 1,631,586 | ⚠️ 99.21% | 100.0% | |
| relay.waow.tech | @zzstoatzz.io | 🇩🇪 Germany (Hetzner) | 207,210 | 1,504,811 | 99.05% | 100.0% | |
| jetstream.waow.tech | @zzstoatzz.io | 🇩🇪 Germany (Hetzner) | 207,200 | 1,661,452 | 99.04% | 100.0% | |
| jetstream2.us-west.bsky.network | Bluesky PBC | 🇺🇸 Oregon (OVH) | 206,890 | 1,624,336 | ⚠️ 98.90% | 99.4% | |
| jet.firehose.stream | @sri.xyz | 🇨🇦 Quebec (OVH) | 206,364 | 1,618,405 | 98.64% | 99.4% | |
| jetstream1.us-west.bsky.network | Bluesky PBC | 🇺🇸 Oregon (OVH) | 206,362 | 1,618,579 | ⚠️ 98.64% | 100.0% | |
| zlay.waow.tech | @zzstoatzz.io | 🇩🇪 Germany (Hetzner) | 205,961 | 1,502,833 | 98.45% | 99.4% | |
| jetstream1.us-east.bsky.network | Bluesky PBC | 🇺🇸 Virginia (OVH) | 205,592 | 1,610,402 | ⚠️ 98.28% | 100.0% | |
| europe.firehose.network | @sri.xyz | 🇵🇱 Warsaw (OVH) | 200,909 | 1,478,535 | 96.04% | 100.0% | |
| frankfurt.firehose.stream | @sri.xyz | 🇩🇪 Frankfurt (OVH) | 200,903 | 1,594,887 | 96.03% | 100.0% | |
| london.firehose.stream | @sri.xyz | 🇬🇧 London (OVH) | 200,903 | 1,594,887 | 96.03% | 100.0% | |
| jetstream2.us-east.bsky.network | Bluesky PBC | 🇺🇸 Virginia (OVH) | 186,723 | 1,425,000 | ⚠️ 89.26% | 99.4% | |
| northamerica.firehose.network | @sri.xyz | 🇺🇸 Virginia (OVH) | 180,801 | 1,241,858 | ⚠️ 86.43% | 100.0% | |
| jetstream.fire.hose.cam | @bad-example.com | 🇨🇦 Montreal (ServaRica) | 100,368 | 599,276 | 47.98% | 100.0% | |
| relay.upcloud.world | UpCloud | 🇵🇱 Warsaw (–) | 75,671 | 538,214 | 36.17% | 100.0% | |
| relay.feeds.blue | @mackuba.eu | 🇩🇪 Germany (Netcup) | 662 | 6,087 | 0.32% | 100.0% | |
| relay.klbr.net | @klbr.net | 🇨🇦 Canada (-) | (no signal received) | 12.4% | |||
| relay.klbr.net | @klbr.net | 🇨🇦 Canada (-) | (no signal received) | 12.4% | |||
1) = firehose (CBOR), = Jetstream, 2 = Jetstream v2
2) Outlier results with suspicious numbers are excluded from calculating the "max users" value, which is why some entries might appear with % larger than 100. "No signal received" means the test runner couldn't make a connection, while 0 events mean that no data was sent over the websocket.
3) Uptime is calculated by making connections to listed servers randomly during the day, around 4 times per day on average for a given source, and recording if a connection was successful and received any data. The % is an average over the last 30 days.