Skip to main content
incident.io

Integration failures due to Cloudflare outage

Degraded Lasted 24m · started · incident.io's page

Level
confirmed
Worst impact
Degraded
Down Index
15of 100

What to do

  • Check whether your product depends on incident.io. 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.
  • Confirm your retries, queues and scheduled jobs caught up after the 24m it lasted.

    Anything that failed between 2025-12-05 09:07 UTC and 2025-12-05 09:30 UTC may need a replay.
  • Subscribe to incident.io's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=incident-io works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from incident.io 3

  1. identified

    We have identified increased error rates with a number of our platform integrations, these relate to an ongoing Cloudflare outage. The list of impacted integrations includes: SAML sign-on, Zoom, Zendesk, Gitlab and Linear, but others may be experiencing degradation as well. On-call notifications and our Slack and Microsoft Teams apps are unaffected.

    provider

  2. monitoring

    Cloudflare has implemented a fix for the issue (https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q) and we've seen recovery. SAML sign ins are now successful, other integration health appears to be recovering. We'll have more updates as and when things change.

    provider

  3. resolved

    Cloudflare have resolved (https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q) the incident. We've seen a recovery in system health - all integrations have returned to normal.

    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-5082868528

Is incident.io still down?

No, this incident was resolved 2025-12-05 09:30 UTC. For incident.io's live state, see https://down.guide/providers/incident-io.

How long did it last?

24m, from 2025-12-05 09:07 UTC to 2025-12-05 09:30 UTC, by the times incident.io posted.

What caused it?

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

Where does this come from?

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