Skip to main content
Discourse

Brief read only during maintenance

Maintenance Lasted 0m · started · Discourse's page

Level
confirmed
Worst impact
Maintenance

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.
  • Check that everything you run on Discourse came back after the window closed 2026-08-14 05:11 UTC.

  • 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

  1. resolved

    August 14, 2026 4:11AM UTC Scheduled - We are currently performing server maintenance. Some sites may experience a period of read-only lasting less than 1 hour. August 14, 2026 4:12AM UTC Active - Scheduled maintenance is starting. August 14, 2026 5:11AM 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-efc2ac39f2

Is this Discourse maintenance still going on?

No, it ended 2026-08-14 05:11 UTC.

How long did it last?

0m, from 2026-08-14 05:11 UTC to 2026-08-14 05:11 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.