Is incident.io down?
No reported issues
From status.incident.io · checked 4 minutes ago · every 5 minutes
An email when it goes down, and when it’s back.
As of 03:36 UTC on 12 November 2026, incident.io's status page reports no issues. Its last reported problem was on 11 November 2026: “Disruption to Slack incident channels and messages”, major outage, for 4 h 25 min from 15:17 UTC.
- Last problem
- 11 Nov · 4 h 25 min
- Problems, last 30 days
- 2
- Typical incident
- 2 h
- Longest in 90 days
- 4 h 25 min · 11 Nov
Uptime
incident.io, last 30 days
99.08 %
Biggest dip: incident.io, 4.4 h of major outage on Nov 11.
Incidents
Started in the last 7 days
1
This week Week before
Latest: incident.io, major outage on Nov 11.
Recovery
Median time back online
3 h 12 min
0 of 2 were over within an hour. Each dot is one incident; the dashed line is the median.
Components 42
All online
- Alert ingestion, processing and paging
- Push notifications
- SMS
- Phone
- Status pages
- Response
- Investigations
- Agent
- API
- Dashboard
- Desktop app
- Insights
- MCP
- Microsoft Teams app
- Mobile app
- Slack app
- Asana
- Atlassian Statuspage
- Azure DevOps
- ClickUp
- Confluence
- Cortex
- Datadog
- GitHub
- Google Calendar
- Google Docs
- Google Meet
- Jira
- Linear
- Okta
- Opsgenie
- OpsLevel
- PagerDuty
- SAML login
- Sentry
- Shortcut
- Splunk
- Vanta
- Zapier
- Zendesk
- Zoom
Last 90 days
3 incidents in 48 days tracked · no reported issues 99.3% of the time · typical incident 2 h
Recent incidents
Times in UTC
- Disruption to Slack incident channels and messages 4 h 25 min
Major outage
- Sentry integration degraded 2 h
Issue
- Login errors for subset of Slack Enterprise Grid customers 1 h 10 min
Issue
Having issues right now
Paribu Humanity (H) Yatırma ve Çekme İşlemleri
Critical
AWS · Bahrain (me-south-1) Region Availability
Critical
AWS · UAE (me-central-1) Region Availability
Critical
GW Sistemas O componente “SAAS Webtrans” e alguns outros componentes estão Inativos
Critical
Popular services
All servicesWhere this comes from
Stackpulse reads incident.io’s official status page at status.incident.io every 5 minutes and keeps 90 days of what changed. We don’t test incident.io ourselves, so a problem shows here once incident.io reports it.
Stackpulse isn’t affiliated with incident.io. Names and logos belong to their owners.
For agents and scripts
The same data as Markdown for AI agents, updated every 30 seconds. With Pro, the API and the MCP server give scripts and AI assistants every service and your own dashboards.