- Level
- confirmed
- Worst impact
- Degraded
- Components
- Flows - US (West), Journey - US (West)
- Regions
- us
- Down Index
- 24of 100
What to do
Check whether you use Bird Flows - US (West), Journey - US (West) in us. 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 2h 43m it lasted.
Anything that failed between 2026-04-07 05:49 UTC and 2026-04-07 08:32 UTC may need a replay.Subscribe to Bird's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=messagebird works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Bird 3
- investigating
We are currently investigating this issue.
provider
- monitoring
We've identified the cause of the issue affecting wait steps in automations. A rapid spike in automation activity outpaced our infrastructure's autoscaling response, leading to a temporary processing backlog. Our systems have since scaled to meet demand and the backlog is expected to clear completely in 30mins.
provider
- resolved
All backlog fully processed.
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-5520523c23
Is Bird still down?
No, this incident was resolved 2026-04-07 08:32 UTC. For Bird's live state, see https://down.guide/messagebird.
How long did it last?
2h 43m, from 2026-04-07 05:49 UTC to 2026-04-07 08:32 UTC, by the times Bird posted.
What was affected?
Bird named Flows - US (West), Journey - US (West) in us.
What caused it?
Bird hasn't published a root cause. If it does, it shows here.
Where does this come from?
Bird's official status page, https://status.bird.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.