Skip to content

Outage tracker / Mastodon / In the US

Is Mastodon down in the US?

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 15:01 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 passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Mastodon at Nov 5, 2026, 3:04 PM UTC.

Over the last 24 hours we completed 249 checks from Ashburn and San Jose and 249 answered cleanly, 100.00% availability.

Of the 2 other regions we check Mastodon from, all 2 read checks passing right now.

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.

What our Ashburn and San Jose probes measured

AshburnChecks passing140 checks in 24h, 100.00%
San JoseChecks passing109 checks in 24h, 100.00%

Last checked Nov 5, 2026, 3:04 PM UTC.

Mastodon from Ashburn and San Jose over the last 30 days

Over the last 30 days, Mastodon answered our Ashburn probe in 988 ms on average, and 1 check in 20 took longer than 1,867 ms.

Over the last 30 days, Mastodon answered our San Jose probe in 1,474 ms on average, and 1 check in 20 took longer than 2,205 ms.

Ranked by average response time across the 4 cities we check Mastodon from, Ashburn 1st, San Jose 3rd; Ashburn was fastest at 988 ms and Tokyo slowest at 1,889 ms.

From Ashburn and San Jose we ran 747 checks of Mastodon in 4 days, and 746 answered cleanly: 99.86% availability.

1 of the 4 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.59% across 244 checks.

In Ashburn local time (EST), Mastodon was slowest around 8 AM, at 1,722 ms on average over the last 14 days, and quickest around 4 AM, at 772 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 5155100.00%1,321 ms
Wed, Nov 4246100.00%1,178 ms
Tue, Nov 324499.59%1,122 ms
Mon, Nov 2102100.00%1,231 ms

Mastodon outages measured from the US

Our Ashburn and San Jose probes measured no confirmed Mastodon outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check Mastodon from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 97 checks
TokyoChecks passing100.00% of 58 checks

Other countries we check Mastodon from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Mastodon's public endpoints. They are not user reports, and they are not Mastodon's own status page.

See Mastodon's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but Mastodon has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter