- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 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 1h 3m it lasted.
Anything that failed between 2026-06-12 14:12 UTC and 2026-06-12 15:15 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 3
- investigating
We are aware of an issue affecting Whatsapp source issues and are actively investigating.
provider
- monitoring
Our engineers are no longer seeing errors related to Whatsapp message send failures persisting in Pylon. The errors originated on Metas side and we are continuing to monitor. We advised attempting to resend the messages that failed since they did not succeed and were not retried due to the error on Metas end.
provider
- resolved
We are no longer seeing the backend errors for Whatsapp message sends and have confirmed that messages are now sending as expected. We apologize for any disruptions and feel free to reach out to support with any further 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-9ce2b5f3e9
Is Pylon still down?
No, this incident was resolved 2026-06-12 15:15 UTC. For Pylon's live state, see https://down.guide/pylon.
How long did it last?
1h 3m, from 2026-06-12 14:12 UTC to 2026-06-12 15:15 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.