- Level
- confirmed
- Worst impact
- Maintenance
- Regions
- us, us-east-2
What to do
Check whether you use Instatus in us, us-east-2. 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-25 15: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.
Updates from Instatus 1
- resolved
Type: Maintenance Duration: 13 minutes Affected Components: Incident response, Slack, On-call, API, Webhooks, Email, Microsoft Teams, Discord, SMS, RSS & Atom, Dashboard, Maintenance Automations, Google Chat, Private status pages, Uptime monitoring, Notifications → Oct 25, 15:12:48 GMT+0 - Completed - Maintenance has completed successfully. Oct 25, 15:00:00 GMT+0 - Identified - We'll switch our backend and API location to us-east-2 because it's usually more stable. We expect a 10 minute downtime that will affect our dashboard and API. Public status pages will continue to be available for your users.
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-8a0c12e9fb
Is this Instatus maintenance still going on?
No, it ended 2025-10-25 15:00 UTC.
How long did it last?
0m, from 2025-10-25 15:00 UTC to 2025-10-25 15:00 UTC, by the times Instatus posted.
What was affected?
Instatus named in us, us-east-2.
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.