Instatus: Scheduled system upgrade

What to do

Check whether you use Instatus Incident response, Slack app, API, Discord and 12 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 2026-06-14 17: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.

resolvedJun 14, 2026, 5:00 PM UTC
Type: Maintenance Duration: 53 minutes Affected Components: Incident response, Slack app, API, Discord, Webhooks, SMS, Microsoft Teams, On-call, Email, Maintenance Automations, Private status pages, RSS & Atom, Google Chat, Dashboard, Uptime monitoring, Slack Jun 14, 17:53:24 GMT+0 - Completed - We just completed the maintenance! No downtime was caused :) Jun 14, 17:00:01 GMT+0 - Identified - Maintenance is now in progress Jun 13, 17:09:07 GMT+0 - Identified - We are upgrading our software stack during that time. We aim for zero downtime, but we're creating this maintenance period just in case. Public status pages will continue to be fully accessible.
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 2026-06-14 17:00 UTC.

How long did it last?

0m, from 2026-06-14 17:00 UTC to 2026-06-14 17:00 UTC, by the times Instatus posted.

What was affected?

Instatus named Incident response, Slack app, API, Discord and 12 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.