- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 100
What to do
Check whether your product depends on Pylon. 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 14h 57m it lasted.
Anything that failed between 2026-05-29 00:52 UTC and 2026-05-29 15:49 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
- investigating
Our engineering team is investigating an issue causing roughly a 2 hour delay in data availability in Analytics. We will post updates here as more information becomes available. Please reach out to Pylon support with any questions.
provider
- resolved
Our engineering team has rolled out a fix for the underlying issue and analytics data is now fully caught up. We apologize for any impact this had on your operation, please reach out to Pylon support with any questions.
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-b32822826e
Is Pylon still down?
No, this incident was resolved 2026-05-29 15:49 UTC. For Pylon's live state, see https://down.guide/pylon.
How long did it last?
14h 57m, from 2026-05-29 00:52 UTC to 2026-05-29 15:49 UTC, by the times Pylon posted.
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.