Latency Issues within the Pylon Platform

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

  Anything that failed between 2026-09-09 23:01 UTC and 2026-09-09 23:23 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 5

1. investigatingSep 9, 2026, 11:01 PM UTC

   We are aware of an issue affecting general Pylon latency issues and are actively investigating.

   provider

2. identifiedSep 9, 2026, 11:03 PM UTC

   We have identified the underlying cause of the issue and are working on a fix right now. We apologize for any inconveniences in existing workflows and customer interactions.

   provider

3. monitoringSep 9, 2026, 11:22 PM UTC

   We have implemented a fix and are monitoring our systems.

   provider

4. resolvedSep 9, 2026, 11:23 PM UTC

   The issue has been resolved and all systems are operational.

   provider

5. resolvedSep 9, 2026, 11:53 PM UTC

   This issue has been resolved. No data was lost as a result of this incident. Between 3:40 PM and 4:20 PM PT, Pylon experienced a delay in syncing new issues to the platform. During this window, new data appeared with up to a 10-minute delay, which caused certain dashboard operations to fail intermittently. _We apologize for the disruption this may have caused to your team's workflow, and we'll continue working to prevent similar issues going forward._

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.