Skip to main content
Pylon

Delays in outbound email delivery

Degraded Lasted 4h 35m · started · Pylon's page

Level
confirmed
Worst impact
Degraded
Down Index
21of 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 35m it lasted.

    Anything that failed between 2026-06-04 23:39 UTC and 2026-06-05 04:14 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

  1. monitoring

    We're investigating delays in outbound email delivery from Pylon related to degraded performance at a third-party email delivery provider that Pylon relies on for sending. Email is still being accepted and queued - outbound messages may be delayed until the provider recovers. No email is being lost. We're monitoring the provider's status closely. The upstream provider is actively working on a resolution. Email continues to be queued and will be delivered once their service is restored. We'll post another update as delivery returns to normal. [https://status.postmarkapp.com/notices/cjagqohtofnqt9ts-email-sending-delays](https://status.postmarkapp.com/notices/cjagqohtofnqt9ts-email-sending-delays "https://status.postmarkapp.com/notices/cjagqohtofnqt9ts-email-sending-delays")

    provider

  2. resolved

    The issue has been resolved and all systems are operational.

    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-32209cee0f

Is Pylon still down?

No, this incident was resolved 2026-06-05 04:14 UTC. For Pylon's live state, see https://down.guide/pylon.

How long did it last?

4h 35m, from 2026-06-04 23:39 UTC to 2026-06-05 04:14 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.