- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 31of 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 4h 39m it lasted.
Anything that failed between 2026-08-17 17:42 UTC and 2026-08-17 22:21 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
- identified
We are seeing codebase search failures within Pylon due to an upstream [Github incident](https://www.githubstatus.com/incidents/zkxwbgr0cnmx), our engineering team is closely monitoring and we will post updates here as they become available. We apologize for any impact this is having on your operations, please reach out to Pylon support with any questions.
provider
- resolved
Github has confirmed the [incident](https://www.githubstatus.com/incidents/zkxwbgr0cnmx) is fully resolved on their end, 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-3694b82022
Is Pylon still down?
No, this incident was resolved 2026-08-17 22:21 UTC. For Pylon's live state, see https://down.guide/pylon.
How long did it last?
4h 39m, from 2026-08-17 17:42 UTC to 2026-08-17 22:21 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.