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-10-19 21:26 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 1 minute ago

Bluesky is answering our probes, but its web surface is running at least 3x its 7-day median from UK and its API is running at least 4x its 7-day median from UK and US-West. Everything else we check answered at its usual speed.

As of Oct 19, 2026, 9:29 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 Oct 19, 2026, 9:29 PM UTC
US-East1861 msChecks passing
US-West1879 msPartially degraded
Europe1183 msChecks passing
Asia-Pacific731 msChecks passing
US-Central1001 msChecks passing
Canada594 msChecks passing
UK1502 msDegraded
Southeast Asia2764 msChecks passing
Australia1197 msChecks passing
South America3092 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.1sp95 · latest
2.5s1.3s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 760ms2026-10-02 UTC: p95 649ms2026-10-03 UTC: p95 659ms2026-10-04 UTC: p95 639ms2026-10-05 UTC: p95 710ms2026-10-06 UTC: p95 722ms2026-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.1s
Sep 20Oct 4Oct 19
US-West
2.1sp95 · 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-09-20 UTC: p95 906ms2026-09-21 UTC: p95 920ms2026-09-22 UTC: p95 937ms2026-09-23 UTC: p95 892ms2026-09-24 UTC: p95 659ms2026-09-25 UTC: p95 728ms2026-09-26 UTC: p95 699ms2026-09-27 UTC: p95 643ms2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 743ms2026-09-30 UTC: p95 791ms2026-10-01 UTC: p95 846ms2026-10-02 UTC: p95 797ms2026-10-03 UTC: p95 806ms2026-10-04 UTC: p95 896ms2026-10-05 UTC: p95 872ms2026-10-06 UTC: p95 858ms2026-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.1s
Sep 20Oct 4Oct 19
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-09-20 UTC: p95 729ms2026-09-21 UTC: p95 742ms2026-09-22 UTC: p95 767ms2026-09-23 UTC: p95 688ms2026-09-24 UTC: p95 742ms2026-09-25 UTC: p95 763ms2026-09-26 UTC: p95 775ms2026-09-27 UTC: p95 740ms2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 899ms2026-09-30 UTC: p95 815ms2026-10-01 UTC: p95 987ms2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 947ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 991ms2026-10-06 UTC: p95 845ms2026-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.1s
Sep 20Oct 4Oct 19
Asia-Pacific
974msp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.3s2026-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 974ms
Sep 20Oct 4Oct 19
US-Central
1.1sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 716ms2026-09-21 UTC: p95 668ms2026-09-22 UTC: p95 635ms2026-09-23 UTC: p95 693ms2026-09-24 UTC: p95 808ms2026-09-25 UTC: p95 693ms2026-09-26 UTC: p95 629ms2026-09-27 UTC: p95 592ms2026-09-28 UTC: p95 747ms2026-09-29 UTC: p95 674ms2026-09-30 UTC: p95 896ms2026-10-01 UTC: p95 651ms2026-10-02 UTC: p95 559ms2026-10-03 UTC: p95 434ms2026-10-04 UTC: p95 366ms2026-10-05 UTC: p95 337ms2026-10-06 UTC: p95 452ms2026-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.1s
Sep 20Oct 4Oct 19
Canada
833msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 756ms2026-09-21 UTC: p95 970ms2026-09-22 UTC: p95 825ms2026-09-23 UTC: p95 785ms2026-09-24 UTC: p95 875ms2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 619ms2026-10-02 UTC: p95 458ms2026-10-03 UTC: p95 531ms2026-10-04 UTC: p95 549ms2026-10-05 UTC: p95 608ms2026-10-06 UTC: p95 621ms2026-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 833ms
Sep 20Oct 4Oct 19
UK
2.1sp95 · 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-09-20 UTC: p95 777ms2026-09-21 UTC: p95 853ms2026-09-22 UTC: p95 877ms2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 976ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 872ms2026-09-30 UTC: p95 845ms2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 654ms2026-10-03 UTC: p95 682ms2026-10-04 UTC: p95 834ms2026-10-05 UTC: p95 754ms2026-10-06 UTC: p95 654ms2026-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.1s
Sep 20Oct 4Oct 19
Southeast Asia
3.2sp95 · 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-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 2.7s2026-09-22 UTC: p95 2.7s2026-09-23 UTC: p95 2.5s2026-09-24 UTC: p95 2.5s2026-09-25 UTC: p95 2.6s2026-09-26 UTC: p95 2.6s2026-09-27 UTC: p95 2.6s2026-09-28 UTC: p95 2.7s2026-09-29 UTC: p95 2.6s2026-09-30 UTC: p95 2.6s2026-10-01 UTC: p95 3.0s2026-10-02 UTC: p95 3.2s2026-10-03 UTC: p95 3.0s2026-10-04 UTC: p95 2.4s2026-10-05 UTC: p95 1.6s2026-10-06 UTC: p95 1.6s2026-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.2s
Sep 20Oct 4Oct 19
Australia
2.1sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 939ms2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.9s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 2.0s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 2.1s2026-10-02 UTC: p95 2.1s2026-10-03 UTC: p95 2.1s2026-10-04 UTC: p95 2.1s2026-10-05 UTC: p95 2.2s2026-10-06 UTC: p95 1.9s2026-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.1s
Sep 20Oct 4Oct 19
South America
3.5sp95 · 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-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.8s2026-09-23 UTC: p95 1.7s2026-09-24 UTC: p95 1.9s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 2.0s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 2.0s2026-10-05 UTC: p95 2s2026-10-06 UTC: p95 1.9s2026-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.5s
Sep 20Oct 4Oct 19

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: Degraded Answering, but 3x slower than its 7-day median.Southeast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIUS-East: Checks passingUS-West: Degraded Answering, but 4x slower than its 7-day median.Europe: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Degraded Answering, but 4x slower than its 7-day median.Southeast 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
    Partially degradedUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1861msstatus code: 200checked: Oct 19, 2026, 9:22 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
      Partially degradedlatency: 1879msstatus code: 200checked: Oct 19, 2026, 9:22 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: 1001msstatus code: 200checked: Oct 19, 2026, 9:17 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: 594msstatus code: 200checked: Oct 19, 2026, 9:21 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: 3092msstatus code: 200checked: Oct 19, 2026, 9:11 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
    DegradedEurope, UK
    • Europe
      Checks passinglatency: 1183msstatus code: 200checked: Oct 19, 2026, 9:27 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
      Degradedlatency: 1502msstatus code: 200checked: Oct 19, 2026, 9:17 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: 731msstatus code: 200checked: Oct 19, 2026, 9:22 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: 2764msstatus code: 200checked: Oct 19, 2026, 9:29 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: 1197msstatus code: 200checked: Oct 19, 2026, 9:26 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

PDS Issues, 3h 47mdeclared on their status page2026-10-15
Jetstream West Maintenance, 1hdeclared on their status page2026-10-13
Jetstream us-east Cutover, 30mdeclared on their status page2026-10-13
Session Issues, 51mdeclared on their status page2026-10-09
Planned Infrastructure Maintenance, 30mdeclared on their status page2026-10-08
Site loading failure, 55mdeclared on their status page2026-10-07
Planned Infrastructure Maintenance, 30mdeclared on their status page2026-10-07
Infrastructure Maintenance, 30mdeclared on their status page2026-09-30

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>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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.