- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us
- Down Index
- 33of 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 1h 50m it lasted.
Anything that failed between 2026-09-28 16:14 UTC and 2026-09-28 18:03 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 2
- monitoring
We have been alerted to an incident with our email provider, affecting US hosted Pylon workspaces, causing delayed processing of inbound delays that began at 8:25 PDT. No messages were lost and were queued for processing. As of 9:03 PDT they have implemented a fix and inbound message processing is now recovering. Delayed messages are being worked through, and processing times are returning to normal. We are continuing to monitor this fix to confirm a full recover.
provider
- resolved
This has been resolved. All inbound email processing have been caught up. No messages have been lost.
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-792dd1ee54
Is Pylon still down?
No, this incident was resolved 2026-09-28 18:03 UTC. For Pylon's live state, see https://down.guide/pylon.
How long did it last?
1h 50m, from 2026-09-28 16:14 UTC to 2026-09-28 18:03 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.