Is Bluesky Down?

No — Bluesky is up

Reachable from all 8 checked regions

Average response time: 210ms

Last checked 2 hours ago · checks run every 6 hours

Official status page: https://status.bsky.app

Bluesky uptime

100%

Last 7 days

99.02%

Last 30 days

99.02%

Last 90 days

240ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 10 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

7-day clean streak

Jul 25 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

294ms

DNS 0ms TCP 2ms TLS 7ms TTFB 291ms

lax

45ms

DNS 0ms TCP 1ms TLS 8ms TTFB 42ms

lhr

290ms

DNS 0ms TCP 1ms TLS 5ms TTFB 287ms

nrt

138ms

DNS 1ms TCP 4ms TLS 4ms TTFB 135ms

ord

113ms

DNS 1ms TCP 1ms TLS 5ms TTFB 111ms

sin

453ms

DNS 0ms TCP 0ms TLS 4ms TTFB 450ms

sjc

46ms

DNS 0ms TCP 1ms TLS 8ms TTFB 43ms

syd

207ms

DNS 2ms TCP 0ms TLS 4ms TTFB 205ms

yyz

140ms

DNS 0ms TCP 0ms TLS 19ms TTFB 137ms

What Bluesky does

Bluesky is a public social network built on the AT Protocol, an open standard that separates account identity from the app used to post. Most people use the bsky.app client together with Bluesky's own hosting, so an outage there stops posting and reading for the majority of users even though the protocol itself allows independent servers.

What an outage looks like

Timelines stop loading or return an empty feed while the app shell still renders. Posting fails with an error and the draft stays in the composer. Notifications and follower counts freeze at an old value. Login fails or existing sessions drop, and search returns nothing. Custom feeds, which are served separately, can break while the following timeline works.

What to do about it

Check status.bsky.app, Bluesky's own status page. Because the network runs on the AT Protocol, confirm where the fault sits: an account hosted on an independent personal data server can keep working when Bluesky's own hosting does not. If a post appears to fail, look at your profile before sending it again, since a duplicate is easy to create and hard to undo.

Is it down for everyone, or just you?

If this page says Bluesky is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Discord (for communities)

Buffer

Hootsuite

Bluesky outage FAQ

Is Bluesky down for everyone or just me?

Check status.bsky.app first, then compare it against the per-region measurements on this page. A fault visible in one region and not others usually points to a network path rather than to Bluesky. If the API answers but the app will not load, the more likely cause is the web client or a stale browser cache rather than the service behind it.

Does a Bluesky outage affect other AT Protocol servers?

Not necessarily. The AT Protocol separates identity, hosting and the app view, so an account on an independent personal data server can stay reachable when Bluesky's own infrastructure fails. In practice most accounts are hosted by Bluesky, so a large outage still looks total to most people. Third-party clients pointed at Bluesky's services fail along with them.

Will I lose posts written during an outage?

A post that returned an error was never published, so it is not lost so much as never sent. Copy the text out of the composer before retrying. Once service returns, check your profile before posting again, because an apparent failure sometimes still reached the network, and posting the same thing twice is the more common outcome.

Why do custom feeds fail when my following feed works?

Custom feeds come from feed generators, which are separate services that anyone can run, including people unaffiliated with Bluesky. A feed can therefore go down on its own while Bluesky is healthy, and the reverse happens too. If only one feed is broken, the fault is almost certainly with that generator rather than with the network.

How we measure this

We request Bluesky's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Bluesky publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Bluesky goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required