Skip to content

Outage tracker / Mastodon

Is Mastodon down?

I'm having a problem

Vendor lists an old incident, not shown as liveWhat Mastodon reports

Mastodon still lists an incident opened on 2026-10-20 with no update since 2026-10-20; we do not show it as live.

As of the last successful poll, 2026-11-05 14:24 UTC.

Mastodon'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.

Checks passingchecked 3 minutes ago

Our checks of Mastodon pass from all 4 regions we check.

As of Nov 5, 2026, 2:24 PM UTC, RealUptime's checks of Mastodon passed in all 4 regions that returned a reading.

Front-door and live API checks

Email me when Mastodon 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 Mastodon's own statement from its status page, with our regional reading beside it.

our check readinglive · checked Nov 5, 2026, 2:24 PM UTC
US-East766 msChecks passing
US-West1837 msChecks passing
Europe789 msChecks passing
Asia-Pacific1958 msChecks passing
their status pagetheir claim, not our reading

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

Mastodon response time, by region

US-East
1.9sp95 · 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-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
US-West
2.6sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 2.6s
Oct 7Oct 21Nov 5
Europe
1.4sp95 · latest
5s2.5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 2.6s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Asia-Pacific
2.8sp95 · 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-11-02 UTC: p95 3.3s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 3.1s2026-11-05 UTC: p95 2.8s
Oct 7Oct 21Nov 5

Check your own site while you wait on Mastodon

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 Mastodon. It cannot diagnose Mastodon's own systems.

What we measured, function by function

Mastodon 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 api 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.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
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
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 766msstatus code: 200checked: Nov 5, 2026, 2:21 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Mastodon normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1837msstatus code: 200checked: Nov 5, 2026, 2:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Mastodon normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionMastodon is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionMastodon is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionMastodon is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 789msstatus code: 200checked: Nov 5, 2026, 2:24 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Mastodon normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionMastodon is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1958msstatus code: 200checked: Nov 5, 2026, 2:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Mastodon normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionMastodon is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionMastodon is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

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

These are unverified reports from people using Mastodon, 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 Mastodon yet, which is not evidence that nothing is wrong.

Recent probe events

Hetzner Connectivity Issues, 33h 2mdeclared on their status page2026-10-31
Networking outage at Hetznerdeclared on their status page2026-10-20
Hetzner Connectivity Issues, 29h 19mdeclared on their status page2026-10-01
Website and API is down, 26mdeclared on their status page2026-09-25
Degraded performance on API and website, 99h 17mdeclared on their status page2026-09-21
Website inaccessible, 26mdeclared on their status page2026-08-19
Elasticsearch issues, 26h 14mdeclared on their status page2026-08-05
Elasticsearch issues, 1h 2mdeclared on their status page2026-06-06

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

We have been measuring Mastodon since November 2, 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 Mastodon covering any window you pick, with our check readings and Mastodon's own claim at the time, side by side.

Full check history for Mastodon: 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

Mastodon uptime by RealUptime's checksLive, from this page's own readings.
[![Mastodon uptime by RealUptime's checks](https://realuptime.io/outages/mastodon/badge.svg?days=30)](https://realuptime.io/outages/mastodon)
<a href="https://realuptime.io/outages/mastodon"><img src="https://realuptime.io/outages/mastodon/badge.svg?days=30" alt="Mastodon 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 Mastodon down?", https://realuptime.io/outages/mastodon. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: live API
https://mastodon.social/api/v1/instance
secondary
https://joinmastodon.org/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: mastodon.social

RealUptime is not affiliated with Mastodon; the name identifies what we checked, and nothing here speaks for Mastodon's own team. We send a single web request to Mastodon from 4 regions on our own schedule and time the response. We do not see inside Mastodon's systems, do not use an account or real transaction, and are not the same signal Mastodon's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Mastodon 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. Mastodon operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 2406 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.