Skip to main content
RudderStack

Monitoring Potential Impact from Azure Outage

Degraded Lasted 6h 50m · started · RudderStack's page

Level
confirmed
Worst impact
Degraded
Down Index
22of 100

What to do

  • Check whether your product depends on RudderStack. 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 6h 50m it lasted.

    Anything that failed between 2025-10-29 17:26 UTC and 2025-10-30 00:15 UTC may need a replay.
  • Subscribe to RudderStack's feed to hear about the next one first. RSS feed

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

Updates from RudderStack 2

  1. monitoring

    We're aware of the ongoing Azure outage. At this time, RudderStack services are not impacted. Our team is actively monitoring the situation and prepared to take mitigation steps if the impact broadens.

    provider

  2. resolved

    This incident has been resolved.

    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-5ae8939963

Is RudderStack still down?

No, this incident was resolved 2025-10-30 00:15 UTC. For RudderStack's live state, see https://down.guide/rudderstack.

How long did it last?

6h 50m, from 2025-10-29 17:26 UTC to 2025-10-30 00:15 UTC, by the times RudderStack posted.

What caused it?

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

Where does this come from?

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