incident.io logo

Is incident.io Down?

MonitoringLive status, outages, and incident history

No. incident.io is up right now.

Every monitored incident.io system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment incident.io breaks

incident.io is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official incident.io status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

incident.io Component Status

The main incident.io systems on this page. All 43 are operational right now.

43operational
Agent
Operational
Alert ingestion, processing and paging
Operational
API
Operational

40 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Asana, Atlassian Statuspage, Azure DevOps, ClickUp, Confluence, Cortex, Dashboard, Datadog, Desktop app, Email, GitHub, Google Calendar, and 28 more.

See all of them free

Component statuses may change independently during partial outages.

Recent incident.io Outages & Incidents

Incident history from the official incident.io status page, including resolution updates.

Increased latency in Microsoft TeamsResolved Aug 20, 2026 · 1h 48mResolved

Latency has now returned to normal. Between 13:00 and 15:08 UTC there were periods of increased latency from some Microsoft APIs. Messages in Microsoft Teams were delivered with increased latency. Our dashboard and mobile app were not affected. --- [2026-08-20T15:31:01Z] (identified) We are continuing to see periods of increased latency with our Microsoft Teams app. All other surfaces, including the dashboard and our mobile app, remain unaffected. --- [2026-08-20T14:42:56Z] (identified) We have identified increased latency in our Microsoft Teams app. We are currently investigating how this is impacting our platform and we will update with more information shortly as we learn more.

Issue with listing alerts in the public API and dashboardResolved Aug 18, 2026 · -138 minResolved

We've now rolled back and listing alerts is working normally again. --- [2026-08-18T13:55:30Z] (identified) We've identified an issue listing alerts. Regular alerting and paging is unaffected.

Delays in webhooks from OpsgenieResolved Aug 3, 2026 · 1h 7mResolved

Opsgenie webhook delivery returned to normal at around 17:48 BST --- [2026-08-03T15:56:51Z] (identified) We have identified increased webhook latency with our Opsgenie integration. We are currently investigating how this is impacting our platform and we will update with more information shortly as we learn more.

incident.io Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a incident.io incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 1 day with incidentsSep 25

Live incident.io Outage Reports

Problems reported by engineers using incident.io. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No incident.io problems reported yet.

Something wrong with incident.io on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About incident.io

incident.io publishes a public status page at status.incident.io covering 25 components, including @incident, Confluence and Okta. PulsAPI tracks incident.io outages, degraded performance and incident history in real time, alongside the rest of your monitoring and observability stack.

Over the past 30 days, PulsAPI has measured incident.io uptime at 100.00%. Response times, incident history, and SLA tracking for incident.io are available on the PulsAPI dashboard.

incident.io Status FAQ

Is incident.io down right now?

The verdict at the top of this page comes from the latest poll of the official incident.io status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if incident.io is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until incident.io recovers.

How do I check incident.io uptime history?

PulsAPI tracks incident.io uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever incident.io changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect incident.io outages?

PulsAPI reads the official incident.io status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual incident.io components?

Yes. PulsAPI monitors 43 individual incident.io components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when incident.io goes down?

Yes. Create a free account and subscribe to incident.io: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with incident.io to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot incident.io problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor incident.io?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so incident.io plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track incident.io with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services