- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 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 36m it lasted.
Anything that failed between 2026-06-24 14:30 UTC and 2026-06-24 15:06 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 4
- investigating
We are aware of an issue affecting some latency with API calls and are actively investigating.
provider
- identified
We have identified the underlying cause of the latency on the API and are working on a fix.
provider
- monitoring
Our engineers have implemented a fix and are monitoring our systems.
provider
- resolved
The issue has been resolved and all systems are operational- thank you for your pateince and we apologize for any disruption to your workflows.
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-b2c149e02a
Is Pylon still down?
No, this incident was resolved 2026-06-24 15:06 UTC. For Pylon's live state, see https://down.guide/pylon.
How long did it last?
36m, from 2026-06-24 14:30 UTC to 2026-06-24 15:06 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.