Skip to content

Outage tracker / Bluesky

Is Bluesky down?

I'm having a problem

Vendor reports no incidentWhat Bluesky reports

Bluesky reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:01 UTC.

Bluesky's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Partially degradedchecked 4 minutes ago

Bluesky is answering our probes, but its API is running at least 3.8x its 7-day median from Europe. Everything else we check answered at its usual speed.

As of Nov 5, 2026, 3:00 PM UTC, RealUptime's checks of Bluesky passed in all 10 regions that returned a reading.

Front-door and live API checks

Email me when Bluesky reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Bluesky's own statement from its status page, with our regional reading beside it.

our check readinglive · checked Nov 5, 2026, 3:00 PM UTC
US-East931 msChecks passing
US-West1242 msChecks passing
Europe1827 msPartially degraded
Asia-Pacific2653 msChecks passing
US-Central428 msChecks passing
Canada1092 msChecks passing
UK492 msChecks passing
Southeast Asia1364 msChecks passing
Australia1845 msChecks passing
South America1900 msChecks passing
their status pagetheir claim, not our reading

Bluesky publishes no status feed we can read, so the only reading here is our check reading on the left.

Bluesky response time, by region

US-East
2.0sp95 · latest
5s2.5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 684ms2026-10-08 UTC: p95 674ms2026-10-09 UTC: p95 574ms2026-10-10 UTC: p95 613ms2026-10-11 UTC: p95 792ms2026-10-12 UTC: p95 692ms2026-10-13 UTC: p95 802ms2026-10-14 UTC: p95 662ms2026-10-15 UTC: p95 753ms2026-10-16 UTC: p95 549ms2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.1s2026-10-23 UTC: p95 902ms2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 803ms2026-10-28 UTC: p95 499ms2026-10-29 UTC: p95 598ms2026-10-30 UTC: p95 473ms2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 2.2s2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
US-West
1.9sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 895ms2026-10-08 UTC: p95 836ms2026-10-09 UTC: p95 917ms2026-10-10 UTC: p95 803ms2026-10-11 UTC: p95 833ms2026-10-12 UTC: p95 823ms2026-10-13 UTC: p95 937ms2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 895ms2026-10-16 UTC: p95 701ms2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 907ms2026-10-24 UTC: p95 835ms2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.2s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 2.2s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
Europe
2.1sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 936ms2026-10-08 UTC: p95 856ms2026-10-09 UTC: p95 966ms2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 721ms2026-10-12 UTC: p95 956ms2026-10-13 UTC: p95 602ms2026-10-14 UTC: p95 752ms2026-10-15 UTC: p95 913ms2026-10-16 UTC: p95 715ms2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 1.0s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 782ms2026-10-28 UTC: p95 868ms2026-10-29 UTC: p95 965ms2026-10-30 UTC: p95 907ms2026-10-31 UTC: p95 842ms2026-11-01 UTC: p95 800ms2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
Asia-Pacific
2.6sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.9s2026-10-14 UTC: p95 2.4s2026-10-15 UTC: p95 2.0s2026-10-16 UTC: p95 1.9s2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 868ms2026-10-19 UTC: p95 985ms2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 3.0s2026-10-23 UTC: p95 2.6s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 2.3s2026-10-26 UTC: p95 2.8s2026-10-27 UTC: p95 2.3s2026-10-28 UTC: p95 2.7s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 2.1s2026-11-02 UTC: p95 3.3s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.8s2026-11-05 UTC: p95 2.6s
Oct 7Oct 21Nov 5
US-Central
866msp95 · latest
2.5s1.3s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 460ms2026-10-08 UTC: p95 389ms2026-10-09 UTC: p95 408ms2026-10-10 UTC: p95 406ms2026-10-11 UTC: p95 458ms2026-10-12 UTC: p95 437ms2026-10-13 UTC: p95 580ms2026-10-14 UTC: p95 495ms2026-10-15 UTC: p95 377ms2026-10-16 UTC: p95 501ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 428ms2026-10-24 UTC: p95 400ms2026-10-25 UTC: p95 532ms2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 928ms2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.2s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 409ms2026-11-04 UTC: p95 1.0s2026-11-05 UTC: p95 866ms
Oct 7Oct 21Nov 5
Canada
1.1sp95 · latest
2.5s1.3s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 565ms2026-10-08 UTC: p95 728ms2026-10-09 UTC: p95 622ms2026-10-10 UTC: p95 621ms2026-10-11 UTC: p95 594ms2026-10-12 UTC: p95 609ms2026-10-13 UTC: p95 654ms2026-10-14 UTC: p95 736ms2026-10-15 UTC: p95 580ms2026-10-16 UTC: p95 500ms2026-10-17 UTC: p95 655ms2026-10-18 UTC: p95 833ms2026-10-19 UTC: p95 884ms2026-10-20 UTC: p95 964ms2026-10-21 UTC: p95 967ms2026-10-22 UTC: p95 2.1s2026-10-23 UTC: p95 565ms2026-10-24 UTC: p95 514ms2026-10-25 UTC: p95 705ms2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
UK
1.3sp95 · latest
2.5s1.3s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 576ms2026-10-08 UTC: p95 674ms2026-10-09 UTC: p95 763ms2026-10-10 UTC: p95 624ms2026-10-11 UTC: p95 593ms2026-10-12 UTC: p95 563ms2026-10-13 UTC: p95 569ms2026-10-14 UTC: p95 569ms2026-10-15 UTC: p95 546ms2026-10-16 UTC: p95 593ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 2.1s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 908ms2026-11-02 UTC: p95 762ms2026-11-03 UTC: p95 947ms2026-11-04 UTC: p95 692ms2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Southeast Asia
2.5sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.9s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.8s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 2.2s2026-10-16 UTC: p95 2.3s2026-10-17 UTC: p95 2.9s2026-10-18 UTC: p95 3.1s2026-10-19 UTC: p95 3.3s2026-10-20 UTC: p95 2.9s2026-10-21 UTC: p95 3.2s2026-10-22 UTC: p95 3.5s2026-10-23 UTC: p95 3.1s2026-10-24 UTC: p95 3.0s2026-10-25 UTC: p95 3.1s2026-10-26 UTC: p95 3.3s2026-10-27 UTC: p95 2.8s2026-10-28 UTC: p95 2.7s2026-10-29 UTC: p95 2.7s2026-10-30 UTC: p95 3.5s2026-10-31 UTC: p95 3.4s2026-11-01 UTC: p95 3.3s2026-11-02 UTC: p95 2.7s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.6s2026-11-05 UTC: p95 2.5s
Oct 7Oct 21Nov 5
Australia
2.5sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.0s2026-10-08 UTC: p95 2.1s2026-10-09 UTC: p95 2.0s2026-10-10 UTC: p95 1.9s2026-10-11 UTC: p95 1.7s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 2.4s2026-10-14 UTC: p95 2.4s2026-10-15 UTC: p95 2.2s2026-10-16 UTC: p95 2.1s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 3.5s2026-10-22 UTC: p95 2.6s2026-10-23 UTC: p95 2.6s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.5s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.4s2026-10-30 UTC: p95 2.7s2026-10-31 UTC: p95 2.6s2026-11-01 UTC: p95 2.6s2026-11-02 UTC: p95 3.6s2026-11-03 UTC: p95 3.5s2026-11-04 UTC: p95 3.6s2026-11-05 UTC: p95 2.5s
Oct 7Oct 21Nov 5
South America
2.6sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.1s2026-10-08 UTC: p95 2.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.9s2026-10-11 UTC: p95 1.8s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 2.2s2026-10-14 UTC: p95 2.3s2026-10-15 UTC: p95 2.1s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 3.4s2026-10-18 UTC: p95 3.6s2026-10-19 UTC: p95 3.5s2026-10-20 UTC: p95 3.7s2026-10-21 UTC: p95 2.8s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 2.4s2026-10-25 UTC: p95 2.5s2026-10-26 UTC: p95 2.8s2026-10-27 UTC: p95 1.5s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 3.2s2026-10-30 UTC: p95 3.2s2026-10-31 UTC: p95 2.8s2026-11-01 UTC: p95 3.0s2026-11-02 UTC: p95 3.1s2026-11-03 UTC: p95 3.4s2026-11-04 UTC: p95 3.7s2026-11-05 UTC: p95 2.6s
Oct 7Oct 21Nov 5

Check your own site while you wait on Bluesky

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Bluesky. It cannot diagnose Bluesky's own systems.

What we measured, function by function

Bluesky answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIUS-East: Checks passingUS-West: Checks passingEurope: Degraded Answering, but 3.8x slower than its 7-day median.Asia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 931msstatus code: 200checked: Nov 5, 2026, 2:56 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Bluesky normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1242msstatus code: 200checked: Nov 5, 2026, 2:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Bluesky normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 428msstatus code: 200checked: Nov 5, 2026, 2:46 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Bluesky normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1092msstatus code: 200checked: Nov 5, 2026, 2:52 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Bluesky normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1900msstatus code: 200checked: Nov 5, 2026, 2:54 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Bluesky normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Partially degradedEurope, UK
    • Europe
      Partially degradedlatency: 1827msstatus code: 200checked: Nov 5, 2026, 2:55 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Bluesky normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 492msstatus code: 200checked: Nov 5, 2026, 3:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Bluesky normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2653msstatus code: 200checked: Nov 5, 2026, 2:48 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Bluesky normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1364msstatus code: 200checked: Nov 5, 2026, 2:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Bluesky normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1845msstatus code: 200checked: Nov 5, 2026, 2:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Bluesky normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Bluesky, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Bluesky yet, which is not evidence that nothing is wrong.

Recent probe events

Goldenear PDS scheduled maintenance, 1hdeclared on their status page2026-11-05
oysterling PDS maintenance, 15mdeclared on their status page2026-11-05
Partial outage, 3h 12mdeclared on their status page2026-11-02
Site slowness/Loading failures, 46mdeclared on their status page2026-10-28
Some Replies Not Visible, 8h 52mdeclared on their status page2026-10-27
Search instability, 27mdeclared on their status page2026-10-26
Web UI instability, 15mdeclared on their status page2026-10-26
Jetstream Instability, 2h 36mdeclared on their status page2026-10-22

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Bluesky since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Bluesky covering any window you pick, with our check readings and Bluesky's own claim at the time, side by side.

Full check history for Bluesky: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Bluesky uptime by RealUptime's checksLive, from this page's own readings.
[![Bluesky uptime by RealUptime's checks](https://realuptime.io/outages/bluesky/badge.svg?days=30)](https://realuptime.io/outages/bluesky)
<a href="https://realuptime.io/outages/bluesky"><img src="https://realuptime.io/outages/bluesky/badge.svg?days=30" alt="Bluesky uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Bluesky down?", https://realuptime.io/outages/bluesky. The readings change with every check, so give the date you read them.

What we check

primary
https://bsky.app/
secondaryfunctional: live API
https://public.api.bsky.app/xrpc/app.bsky.actor.getProfile?actor=bsky.app
secondary
https://status.bsky.app/

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: bsky.app

RealUptime is not affiliated with Bluesky; the name identifies what we checked, and nothing here speaks for Bluesky's own team. We send a single web request to Bluesky from 10 regions on our own schedule and time the response. We do not see inside Bluesky's systems, do not use an account or real transaction, and are not the same signal Bluesky's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Bluesky is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.