Showing observation from: 2026-10-08 18:00:02 UTC (3600s)
| Host | API 1 | Run by | Location | Users | Events | % of max 2 | Uptime 3 |
|---|---|---|---|---|---|---|---|
| relay.bas.sh | @bas.sh | 🇩🇪 Germany (Hetzner) | 207,058 | 1,534,914 | 100.00% | 100.0% | |
| europe.firehose.network | @sri.xyz | 🇵🇱 Warsaw (OVH) | 207,009 | 1,533,790 | 99.98% | 100.0% | |
| london.firehose.stream | @sri.xyz | 🇬🇧 London (OVH) | 207,003 | 1,599,190 | 99.97% | 100.0% | |
| frankfurt.firehose.stream | @sri.xyz | 🇩🇪 Frankfurt (OVH) | 207,003 | 1,599,190 | 99.97% | 100.0% | |
| chennai.firehose.stream | @sri.xyz | 🇮🇳 Mumbai (OVH) | 206,977 | 1,599,065 | 99.96% | 100.0% | |
| nyc.firehose.stream | @sri.xyz | 🇺🇸 Virginia (OVH) | 206,956 | 1,599,088 | 99.95% | 100.0% | |
| sfo.firehose.stream | @sri.xyz | 🇺🇸 Oregon (OVH) | 206,946 | 1,599,025 | 99.95% | 100.0% | |
| jetstream1.us-east.bsky.network | Bluesky PBC | 🇺🇸 Virginia (OVH) | 206,826 | 1,598,183 | 99.89% | 100.0% | |
| relay1.us-east.bsky.network | Bluesky PBC | 🇺🇸 Virginia (–) | 206,818 | 1,532,927 | 99.88% | 99.4% | |
| bsky.network | Bluesky PBC | 🇺🇸 California (–) | 206,816 | 1,532,886 | 99.88% | 100.0% | |
| relay1.us-west.bsky.network | Bluesky PBC | 🇺🇸 California (–) | 206,816 | 1,532,927 | 99.88% | 100.0% | |
| jet.firehose.stream | @sri.xyz | 🇨🇦 Quebec (OVH) | 206,793 | 1,597,931 | 99.87% | 99.4% | |
| jetstream2.us-west.bsky.network | Bluesky PBC | 🇺🇸 Oregon (OVH) | 206,783 | 1,597,887 | 99.87% | 99.4% | |
| jetstream1.us-west.bsky.network | Bluesky PBC | 🇺🇸 Oregon (OVH) | 206,769 | 1,597,812 | 99.86% | 100.0% | |
| jetstream1.us-east.fire.hose.cam | @bad-example.com | 🇺🇸 Virginia (Hetzner) | 206,769 | 1,597,812 | 99.86% | 100.0% | |
| relay3.fr.hose.cam | @bad-example.com | 🇫🇷 France (OVH) | 206,748 | 1,531,902 | 99.85% | 100.0% | |
| jetstream2.fr.hose.cam | @bad-example.com | 🇩🇪 Germany (Hetzner) | 206,740 | 1,597,260 | 99.85% | 100.0% | |
| relay.fire.hose.cam | @bad-example.com | 🇨🇦 Montreal (ServaRica) | 206,739 | 1,535,232 | 99.85% | 100.0% | |
| relay1.eurosky.network | Eurosky | 🇩🇪 Germany (Hetzner) | 206,720 | 1,531,873 | 99.84% | 100.0% | |
| jetstream1.eurosky.network | Eurosky | 🇩🇪 Germany (Hetzner) | 206,708 | 1,597,233 | 99.83% | 100.0% | |
| jetstream.us-west.bsky.network | 2 | Bluesky PBC | 🇺🇸 California (–) | 206,702 | 1,595,342 | 99.83% | 100.0% |
| jetstream.us-east.bsky.network | 2 | Bluesky PBC | 🇺🇸 Virginia (–) | 206,698 | 1,595,316 | 99.83% | 99.4% |
| relay.klbr.net | @klbr.net | 🇨🇦 Canada (-) | 206,686 | 1,591,915 | 99.82% | 12.4% | |
| relay.klbr.net | @klbr.net | 🇨🇦 Canada (-) | 206,668 | 1,527,409 | 99.81% | 12.4% | |
| relay.t4tlabs.net | @isla.pet | 🇨🇦 Toronto (Xenyth) | 206,605 | 1,532,832 | 99.78% | 100.0% | |
| atproto.africa | Blacksky Algorithms | 🇺🇸 Virginia (OVH) | 206,453 | 1,525,278 | 99.71% | 95.3% | |
| relay.waow.tech | @zzstoatzz.io | 🇩🇪 Germany (Hetzner) | 204,996 | 1,513,291 | 99.00% | 100.0% | |
| jetstream.waow.tech | @zzstoatzz.io | 🇩🇪 Germany (Hetzner) | 204,988 | 1,577,921 | 99.00% | 100.0% | |
| zlay.waow.tech | @zzstoatzz.io | 🇩🇪 Germany (Hetzner) | 201,813 | 1,488,816 | 97.47% | 99.4% | |
| asia.firehose.network | @sri.xyz | 🇮🇳 Mumbai (OVH) | 189,176 | 1,350,021 | ⚠️ 91.36% | 100.0% | |
| jetstream2.us-east.bsky.network | Bluesky PBC | 🇺🇸 Virginia (OVH) | 161,780 | 1,512,160 | ⚠️ 78.13% | 99.4% | |
| northamerica.firehose.network | @sri.xyz | 🇺🇸 Virginia (OVH) | 155,686 | 1,022,919 | ⚠️ 75.19% | 100.0% | |
| jetstream.fire.hose.cam | @bad-example.com | 🇨🇦 Montreal (ServaRica) | 100,542 | 585,704 | 48.56% | 100.0% | |
| relay.upcloud.world | UpCloud | 🇵🇱 Warsaw (–) | 72,115 | 522,060 | 34.83% | 100.0% | |
| relay.feeds.blue | @mackuba.eu | 🇩🇪 Germany (Netcup) | 644 | 5,536 | 0.31% | 100.0% |
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.