Skip to main content
RudderStack

AWS Cloud Provider Outage

Degraded Lasted 0m · started · RudderStack's page

Level
confirmed
Worst impact
Degraded
Down Index
8of 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 0m it lasted.

    Anything that failed between 2025-10-20 10:18 UTC and 2025-10-20 07:30 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 1

  1. resolved

    We experienced an issue with our AWS cloud provider, which caused temporary disruptions to web app login functionality. https://health.aws.amazon.com/health/status Users may have been unable to log in during this period. Ingestion services were not impacted, all data continued to flow and process as expected.

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

Is RudderStack still down?

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

How long did it last?

0m, from 2025-10-20 10:18 UTC to 2025-10-20 07:30 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.