Skip to content

Outage tracker / Bluesky

Is Bluesky down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Bluesky from all 10 regions we check.

As of Oct 5, 2026, 9:03 PM UTC, Bluesky answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Bluesky (since Aug 20, 2026).

Email me the next time we see Bluesky go down

Measured by our own probes from ten regions, not Bluesky's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 5, 2026, 9:03 PM UTC
US-East622 msOperational
US-West797 msOperational
Europe553 msOperational
Asia-Pacific839 msOperational
US-Central164 msOperational
Canada707 msOperational
UK690 msOperational
Southeast Asia1174 msOperational
Australia1389 msOperational
South America1831 msOperational
their status pagetheir claim, not our reading

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

Bluesky response time, by region

US-East
672msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 962ms2026-09-07 UTC: p95 988ms2026-09-08 UTC: p95 976ms2026-09-09 UTC: p95 878ms2026-09-10 UTC: p95 959ms2026-09-11 UTC: p95 970ms2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 994ms2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.2s2026-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 672ms
Sep 6Sep 20Oct 5
US-West
870msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 746ms2026-09-07 UTC: p95 515ms2026-09-08 UTC: p95 532ms2026-09-09 UTC: p95 296ms2026-09-10 UTC: p95 440ms2026-09-11 UTC: p95 363ms2026-09-12 UTC: p95 386ms2026-09-13 UTC: p95 496ms2026-09-14 UTC: p95 454ms2026-09-15 UTC: p95 843ms2026-09-16 UTC: p95 832ms2026-09-17 UTC: p95 981ms2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 952ms2026-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 870ms
Sep 6Sep 20Oct 5
Europe
1.0sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 574ms2026-09-07 UTC: p95 560ms2026-09-08 UTC: p95 577ms2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 881ms2026-09-15 UTC: p95 805ms2026-09-16 UTC: p95 713ms2026-09-17 UTC: p95 683ms2026-09-18 UTC: p95 770ms2026-09-19 UTC: p95 740ms2026-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 1.0s
Sep 6Sep 20Oct 5
Asia-Pacific
1.3sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 914ms2026-09-07 UTC: p95 878ms2026-09-08 UTC: p95 636ms2026-09-09 UTC: p95 601ms2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 991ms2026-09-13 UTC: p95 892ms2026-09-14 UTC: p95 901ms2026-09-15 UTC: p95 957ms2026-09-16 UTC: p95 996ms2026-09-17 UTC: p95 997ms2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.1s2026-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.3s
Sep 6Sep 20Oct 5
US-Central
339msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 624ms2026-09-07 UTC: p95 565ms2026-09-08 UTC: p95 742ms2026-09-09 UTC: p95 585ms2026-09-10 UTC: p95 599ms2026-09-11 UTC: p95 633ms2026-09-12 UTC: p95 792ms2026-09-13 UTC: p95 657ms2026-09-14 UTC: p95 703ms2026-09-15 UTC: p95 757ms2026-09-16 UTC: p95 626ms2026-09-17 UTC: p95 685ms2026-09-18 UTC: p95 681ms2026-09-19 UTC: p95 657ms2026-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 339ms
Sep 6Sep 20Oct 5
Canada
608msp95 · 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-06 UTC: p95 721ms2026-09-07 UTC: p95 675ms2026-09-08 UTC: p95 663ms2026-09-09 UTC: p95 782ms2026-09-10 UTC: p95 762ms2026-09-11 UTC: p95 719ms2026-09-12 UTC: p95 774ms2026-09-13 UTC: p95 797ms2026-09-14 UTC: p95 775ms2026-09-15 UTC: p95 730ms2026-09-16 UTC: p95 831ms2026-09-17 UTC: p95 674ms2026-09-18 UTC: p95 774ms2026-09-19 UTC: p95 797ms2026-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 608ms
Sep 6Sep 20Oct 5
UK
738msp95 · latest
5s2.5s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 576ms2026-09-07 UTC: p95 814ms2026-09-08 UTC: p95 626ms2026-09-09 UTC: p95 832ms2026-09-10 UTC: p95 862ms2026-09-11 UTC: p95 989ms2026-09-12 UTC: p95 834ms2026-09-13 UTC: p95 2.9s2026-09-14 UTC: p95 788ms2026-09-15 UTC: p95 817ms2026-09-16 UTC: p95 819ms2026-09-17 UTC: p95 881ms2026-09-18 UTC: p95 854ms2026-09-19 UTC: p95 839ms2026-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 738ms
Sep 6Sep 20Oct 5
Southeast Asia
1.6sp95 · 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-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 1.7s2026-09-09 UTC: p95 1.7s2026-09-10 UTC: p95 1.6s2026-09-11 UTC: p95 1.9s2026-09-12 UTC: p95 2.0s2026-09-13 UTC: p95 4.1s2026-09-14 UTC: p95 1.8s2026-09-15 UTC: p95 2.1s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.8s2026-09-18 UTC: p95 1.8s2026-09-19 UTC: p95 1.7s2026-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.6s
Sep 6Sep 20Oct 5
Australia
2.3sp95 · 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-06 UTC: p95 1.0s2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 977ms2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 926ms2026-09-19 UTC: p95 1.2s2026-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.3s
Sep 6Sep 20Oct 5
South America
2.0sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 2.0s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 2.0s2026-09-14 UTC: p95 1.7s2026-09-15 UTC: p95 1.9s2026-09-16 UTC: p95 1.8s2026-09-17 UTC: p95 2.4s2026-09-18 UTC: p95 2.0s2026-09-19 UTC: p95 2.0s2026-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 2.0s
Sep 6Sep 20Oct 5

Is it Bluesky, or is it you?

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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 622msstatus code: 200checked: Oct 5, 2026, 8:59 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
      Operationallatency: 797msstatus code: 200checked: Oct 5, 2026, 8:58 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
      Operationallatency: 164msstatus code: 200checked: Oct 5, 2026, 8:55 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
      Operationallatency: 707msstatus code: 200checked: Oct 5, 2026, 8:50 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
    Operationallatency: 1831msstatus code: 200checked: Oct 5, 2026, 9:03 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 553msstatus code: 200checked: Oct 5, 2026, 8:59 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
      Operationallatency: 690msstatus code: 200checked: Oct 5, 2026, 8:48 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 839msstatus code: 200checked: Oct 5, 2026, 8:55 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
      Operationallatency: 1174msstatus code: 200checked: Oct 5, 2026, 8:57 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
      Operationallatency: 1389msstatus code: 200checked: Oct 5, 2026, 8:48 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 outages

No outages on record yet for Bluesky.

measured 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 measurements and Bluesky's own claim at the time, side by side.

Full availability history for Bluesky: 90-day availability by region, month-by-month uptime, and every incident on record.

Put this badge in your README

Bluesky uptime measured by RealUptimeLive, from this page's own readings.
[![Bluesky uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Bluesky's SLA implies, from our measurement

At or above your target

We measured none of downtime for Bluesky over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Bluesky's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

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/
RealUptime is not affiliated with Bluesky; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.