- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 23of 100
What to do
Check whether you use Pylon 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 28m it lasted.
Anything that failed between 2026-07-06 20:00 UTC and 2026-07-06 22:28 UTC may need a replay.Subscribe to Pylon's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=pylon works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Pylon 3
- investigating
We are aware of an issue impacting US customer inbound email delays and are actively tracking. Our upstream vendor posted on their status page here.
provider
- monitoring
Our upstream provider identified the issue and deployed a fix. We will continue to monitor.
provider
- resolved
The issue has been resolved and all systems are operational.
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-b0bd729136
Is Pylon still down?
No, this incident was resolved 2026-07-06 22:28 UTC. For Pylon's live state, see https://down.guide/pylon.
How long did it last?
2h 28m, from 2026-07-06 20:00 UTC to 2026-07-06 22:28 UTC, by the times Pylon posted.
What was affected?
Pylon named in us.
What caused it?
Pylon hasn't published a root cause. If it does, it shows here.
Where does this come from?
Pylon's official status page, https://status.usepylon.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.