- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 18of 100
What to do
Check whether your product depends on Discourse. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-09-23 10:00 UTC and 2026-09-23 10:00 UTC may need a replay.Subscribe to Discourse's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=discourse works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Discourse 1
- resolved
September 17, 2026 11:40AM UTC Scheduled - We will be performing some network failover testing for compliance purposes. Some sites may experience a brief outage while the failover occurs. We expect the interruption to last no more than 15 minutes. September 23, 2026 9:00AM UTC Active - Scheduled maintenance is starting. September 23, 2026 10:00AM UTC Completed - Scheduled maintenance is complete.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-10425f917d
Is Discourse still down?
No, this incident was resolved 2026-09-23 10:00 UTC. For Discourse's live state, see https://down.guide/discourse.
How long did it last?
0m, from 2026-09-23 10:00 UTC to 2026-09-23 10:00 UTC, by the times Discourse posted.
What caused it?
Discourse hasn't published a root cause. If it does, it shows here.
Where does this come from?
Discourse's official status page, https://status.discourse.org, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.