Instatus: Data migration

What to do

Check whether you use Instatus Public status pages, Incident response, Slack, Public status pages and 14 more. 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 Instatus came back after the window closed 2025-10-05 16:00 UTC.
Subscribe to Instatus's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=instatus works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

resolvedOct 5, 2025, 4:00 PM UTC
Type: Maintenance Duration: 1 hour and 6 minutes Affected Components: Public status pages, Incident response, Slack, Public status pages, Slack app, On-call, Private status pages, API, Maintenance Automations, Webhooks, Email, Microsoft Teams, Discord, SMS, Google Chat, RSS & Atom, Dashboard, Uptime monitoring Oct 5, 17:06:06 GMT+0 - Completed - Maintenance has completed successfully. Oct 5, 16:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 5, 16:00:00 GMT+0 - Identified - We'll be having a data migration in order to improve our performance. We expect no downtime, but we're scheduling this maintenance just in case.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is this Instatus maintenance still going on?

No, it ended 2025-10-05 16:00 UTC.

How long did it last?

0m, from 2025-10-05 16:00 UTC to 2025-10-05 16:00 UTC, by the times Instatus posted.

What was affected?

Instatus named Public status pages, Incident response, Slack, Public status pages and 14 more.

What caused it?

Instatus hasn't published a root cause. If it does, it shows here.

Where does this come from?

Instatus's official status page, https://instat.us, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.