- 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 16h 34m it lasted.
Anything that failed between 2026-05-27 23:11 UTC and 2026-05-28 15:45 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
Slack is experiencing [an incident](https://slack-status.com/2026-05-27) causing latency in all services and our engineering team is monitoring. We do not expect any data loss as a result of this and events will be processed when Pylon receives them as normal. We will post updates here as they become available.
provider
- resolved
Slack marked [the incident](https://slack-status.com/2026-05/46d9d5d41fbedd9f) as resolved as of 8:22a PDT, we appreciate your patience while their team worked on a fix. 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-9364790f25
Is Pylon still down?
No, this incident was resolved 2026-05-28 15:45 UTC. For Pylon's live state, see https://down.guide/pylon.
How long did it last?
16h 34m, from 2026-05-27 23:11 UTC to 2026-05-28 15:45 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.