- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Warehouses
- Down Index
- 28of 100
What to do
Check whether you use RudderStack Warehouses. 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 1h 1m it lasted.
Anything that failed between 2025-03-03 09:00 UTC and 2025-03-03 10:00 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 3
- investigating
We are currently investigating this issue.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- resolved
This incident has been resolved. During the migration of our internal database, certain custom configurations from the previous version were not restored in the new setup. This led to degraded service performance, causing failing health checks and an increase in service restarts.
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-bfdd79f880
Is RudderStack still down?
No, this incident was resolved 2025-03-03 10:00 UTC. For RudderStack's live state, see https://down.guide/rudderstack.
How long did it last?
1h 1m, from 2025-03-03 09:00 UTC to 2025-03-03 10:00 UTC, by the times RudderStack posted.
What was affected?
RudderStack named Warehouses.
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.