Skip to main content
Pylon

Delays in scheduled event processing

Degraded Lasted 38m · started · Pylon's page

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 38m it lasted.

    Anything that failed between 2026-05-26 18:07 UTC and 2026-05-26 18: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 4

  1. investigating

    Our engineering team is investigating an issue causing delays in processing some events within Pylon. We will post updates here and update impacted components as we have more information. Please reach out to Pylon support with any questions.

    provider

  2. identified

    Our engineering team has identified the underlying cause and is working on a fix. This is affecting scheduled events (e.g. time delay triggers, scheduled messages and broadcasts, warehouse sync, etc.) and we do not anticipate any data loss as a result of this. Once the underlying issue is addressed, scheduled events will be processed. We apologize for any impact this is having on your operations, please reach out to Pylon support with any questions.

    provider

  3. monitoring

    Our engineering team has rolled out a fix, we are seeing queued events processing and we are monitoring. We will post another update here once we have confirmed this has been fully resolved. Please reach out to Pylon support with any questions.

    provider

  4. resolved

    Our engineering team has confirmed that this is now fully resolved - all queued events have been processed and new scheduled events are processing as normal. We appreciate your patience while we worked to address this, 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-12b047c66c

Is Pylon still down?

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

How long did it last?

38m, from 2026-05-26 18:07 UTC to 2026-05-26 18: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.