Is Bluesky down?
Bluesky is up.
Our last check reached bsky.app and got a healthy response.
The numbers
Availability and response time for Bluesky over the last 24 hours.
Availability
100%
144 checks, none failed
Avg response
204 ms
Mean of every check
Slowest
429 ms
Worst single check
Incidents
0
Runs of failing checks
Downtime
None
Estimated from samples
Downtime is estimated from 10-minute samples, so figures are accurate to within one check interval.
Over time
Every check we ran, and how long each one took.
Availability
- All checks passed
- Some checks failed
- All checks failed
Response time
Where the time goes
"Is it down?" is usually really "it feels broken — what's wrong with it?" This is the answer: every millisecond of a request to bsky.app, broken into the four phases it actually spends time in.
- DNS
- 3 ms2%
- TCP + TLS
- 49 ms24%
- Time to first byte
- 152 ms74%
- Download
- 0 ms0%
Resolving the hostname to an IP address.
Opening the connection and completing the TLS handshake.
Waiting for the server to start responding. Usually the server thinking.
Transferring the response body.
Averaged over the last 24 hours. The four phases add up to the total response time of 204 ms.
Incidents
Every time a check against bsky.app failed in the last 30 days, grouped into incidents.
No incidents recorded for Bluesky.
Every check we’ve run against Bluesky has passed.
This page is a Checkly monitor.
Not a mockup of one. Everything above is produced by the monitor below, running every 10 minutes from N. Virginia and Frankfurt. It lives in a repo, gets code-reviewed, and deploys from CI — the same way you would monitor your own service.
That’s the whole product. Monitoring you can read, diff, and version.
How we check Bluesky
A real request to the endpoint that matters, every 10 minutes — measured, not crowd-sourced.
What we actually do
- We send a real HTTP GET to
https://bsky.social/xrpc/com.atproto.server.describeServerevery 10 minutes. - We run it from two datacenters: N. Virginia and Frankfurt.
- It passes if the endpoint answers with a status below 400 within 10 seconds. Slower than 3 seconds is “degraded”, not down.
- A single failed check isn’t a verdict. We retry it from the other region before recording anything, so a transient blip never shows here as an outage.
- We probe the AT Protocol server-description endpoint Bluesky clients call, rather than the web app shell. If it fails, the network entry service is down.
What a green check means
- Bluesky answered a real request from both N. Virginia and Frankfurt — an actual measurement, not complaints counted from a crowd.
- We probe the endpoint that fails when Bluesky fails, so a green check tracks the part you depend on, not a marketing page that stays up regardless.
- Checks run around the clock, every 10 minutes, on the same infrastructure Checkly customers monitor production with.
Frequently asked
No. Our most recent check reached https://bsky.social/xrpc/com.atproto.server.describeServer and got a healthy response. We check every 10 minutes from N. Virginia and Frankfurt.
We run a real HTTP request against https://bsky.social/xrpc/com.atproto.server.describeServer every 10 minutes from N. Virginia and Frankfurt, using Checkly's synthetic monitoring. A check passes when the endpoint returns a status below 400 within 10 seconds. We are not counting user reports — we are measuring the actual response.
We check Bluesky from N. Virginia and Frankfurt. If it answers us but not you, the problem is usually specific to your network, ISP, region, or account rather than Bluesky itself.
Downdetector counts user reports — how many people are complaining. We run an actual synthetic check against the service and report what the wire says. Reports lag the outage and can be noisy; a probe either gets a response or it doesn't.