Pylon Outage History

Pylon is up right now

Pylon had 42 outages in the last 2 years — averaging 1.7 incidents per month.

There were 42 Pylon outages since October 20, 2025. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.usepylon.com

Minor September 9, 2026

Latency Issues within the Pylon Platform

Detected by Pingoru
Sep 09, 2026, 11:53 PM UTC
Resolved
Sep 09, 2026, 11:53 PM UTC
Duration
—
Affected: Dashboard
Timeline · 5 updates
  1. investigating Sep 09, 2026, 11:01 PM UTC

    Status: Investigating We are aware of an issue affecting general Pylon latency issues and are actively investigating. Affected components Dashboard (Full outage)

  2. identified Sep 09, 2026, 11:03 PM UTC

    Status: Identified 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. Affected components Dashboard (Full outage)

  3. monitoring Sep 09, 2026, 11:22 PM UTC

    Status: Monitoring We have implemented a fix and are monitoring our systems. Affected components Dashboard (Full outage)

  4. resolved Sep 09, 2026, 11:23 PM UTC

    Status: Resolved The issue has been resolved and all systems are operational. Affected components Dashboard (Operational)

  5. resolved Sep 09, 2026, 11:53 PM UTC

    Status: Resolved 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. Affected components Dashboard (Operational)

Read the full incident report →

Minor September 8, 2026

General error messages navigating on tickets

Detected by Pingoru
Sep 08, 2026, 01:35 PM UTC
Resolved
Sep 08, 2026, 01:35 PM UTC
Duration
—
Affected: Dashboard
Timeline · 4 updates
  1. investigating Sep 08, 2026, 01:14 PM UTC

    Status: Investigating We are aware of an issue where an Error message appears when navigating on tickets and are actively investigating. Affected components Dashboard (Degraded performance)

  2. identified Sep 08, 2026, 01:19 PM UTC

    Status: Identified Our engineers have identified the underlying cause of the issue and are working on a fix. Affected components Dashboard (Degraded performance)

  3. monitoring Sep 08, 2026, 01:28 PM UTC

    Status: Monitoring We have implemented a fix for the error messages and are monitoring our systems. Affected components Dashboard (Degraded performance)

  4. resolved Sep 08, 2026, 01:35 PM UTC

    Status: Resolved The issue has been resolved and all systems are operational. Affected components Dashboard (Operational)

Read the full incident report →

Minor August 18, 2026

Analytics dashboard loading issues

Detected by Pingoru
Aug 18, 2026, 05:40 PM UTC
Resolved
Aug 18, 2026, 05:40 PM UTC
Duration
—
Affected: Analytics
Timeline · 4 updates
  1. investigating Aug 18, 2026, 05:23 PM UTC

    Status: Investigating Our engineering team is investigating loading issues in Analytics. We will post updates here as they are available. We apologize for any impact this is having on your operations, please reach out to Pylon support with any questions. Affected components Analytics (Degraded performance)

  2. identified Aug 18, 2026, 05:31 PM UTC

    Status: Identified Our engineering team has rolled out a fix and we are seeing Analytics dashboards recover. We are continuing to monitor and will post another update once we have confirmed this is fully resolved. Please reach out to Pylon support with any questions. Affected components Analytics (Degraded performance)

  3. monitoring Aug 18, 2026, 05:32 PM UTC

    Status: Monitoring Our engineering team has rolled out a fix and we are seeing Analytics dashboards recover. We are continuing to monitor and will post another update once we have confirmed this is fully resolved. Please reach out to Pylon support with any questions. Affected components Analytics (Degraded performance)

  4. resolved Aug 18, 2026, 05:40 PM UTC

    Status: Resolved Our engineering team has confirmed that this is now fully resolved. We apologize for any impact this had on your operations, please reach out to Pylon support with any questions. Affected components Analytics (Operational)

Read the full incident report →

Minor August 17, 2026

Codebase search failures

Detected by Pingoru
Aug 17, 2026, 10:21 PM UTC
Resolved
Aug 17, 2026, 10:21 PM UTC
Duration
—
Affected: Codebase
Timeline · 2 updates
  1. identified Aug 17, 2026, 05:42 PM UTC

    Status: Identified We are seeing codebase search failures within Pylon due to an upstream Github incident: https://www.githubstatus.com/incidents/zkxwbgr0cnmx, our engineering team is closely monitoring and we will post updates here as they become available. We apologize for any impact this is having on your operations, please reach out to Pylon support with any questions. Affected components Codebase (Partial outage)

  2. resolved Aug 17, 2026, 10:21 PM UTC

    Status: Resolved Github has confirmed the incident: https://www.githubstatus.com/incidents/zkxwbgr0cnmx is fully resolved on their end, please reach out to Pylon support with any questions. Affected components Codebase (Operational)

Read the full incident report →

Minor July 15, 2026

Phones/SMS features not functioning

Detected by Pingoru
Jul 15, 2026, 09:45 PM UTC
Resolved
Jul 15, 2026, 09:45 PM UTC
Duration
—
Affected: Phones
Timeline · 3 updates
  1. identified Jul 15, 2026, 06:40 PM UTC

    Status: Identified Our upstream Phones/SMS vendor has an ongoing incident: https://status.telnyx.com/ preventing voice calling and SMS from functioning within Pylon. We will post updates here as soon as they are available from our vendor. We apologize for any impact this is having on your operations, please reach out to Pylon support with any questions. Affected components Phones (Partial outage)

  2. monitoring Jul 15, 2026, 08:46 PM UTC

    Status: Monitoring Our upstream Phones/SMS vendor has moved their ongoing incident: https://status.telnyx.com/ to monitoring. Phone/SMS functionality has been restored within Pylon and we will post another update once they have fully resolved the incident. Please reach out to Pylon support with any questions. Affected components Phones (Operational)

  3. resolved Jul 15, 2026, 09:45 PM UTC

    Status: Resolved Our vendor has confirmed this is now fully resolved and all Phone and SMS functionality within Pylon has been restored. We apologize for any impact this had on your operations, please reach out to Pylon support with any questions. Affected components Phones (Operational)

Read the full incident report →

Minor July 15, 2026

Delays in Search on the platform

Detected by Pingoru
Jul 15, 2026, 08:25 PM UTC
Resolved
Jul 15, 2026, 08:25 PM UTC
Duration
—
Affected: Dashboard
Timeline · 6 updates
  1. investigating Jul 15, 2026, 05:42 PM UTC

    Status: Investigating Our engineering team is investigating an issue causing a delay in search results appearing within the platform. We will post updates as they become available, please reach out to Pylon support with any questions. Affected components Dashboard (Degraded performance)

  2. monitoring Jul 15, 2026, 05:47 PM UTC

    Status: Monitoring Our engineering team has implemented a fix and search has recovered. We are continuing to monitor and will share another update once we have confirmed this is fully resolved. We apologize for any impact this had on your operations, please reach out to Pylon support with any questions. Affected components Dashboard (Operational)

  3. resolved Jul 15, 2026, 06:28 PM UTC

    Status: Resolved Our engineering team has confirmed this is fully resolved. We apologize for any impact this had on your operations, please reach out to Pylon support with any questions. Affected components Dashboard (Operational)

  4. identified Jul 15, 2026, 07:01 PM UTC

    Status: Identified Our engineering team is continuing to work on a fix for intermittent delays in search results. We will post updates here as they become available, please reach out to Pylon support with any questions. Affected components Dashboard (Degraded performance)

  5. monitoring Jul 15, 2026, 07:17 PM UTC

    Status: Monitoring Our engineering team has rolled out an additional fix and we are monitoring. We will share another update once we have confirmed this is fully resolved. We apologize for any impact this had on your operations, please reach out to Pylon support with any questions. Affected components Dashboard (Operational)

  6. resolved Jul 15, 2026, 08:25 PM UTC

    Status: Resolved Our engineering team has confirmed that this is now fully resolved. We apologize for any impact this had on your operations, please reach out to Pylon support with any questions. Affected components Dashboard (Operational)

Read the full incident report →

Minor July 12, 2026

Dashboard Login failures

Detected by Pingoru
Jul 12, 2026, 03:44 PM UTC
Resolved
Jul 12, 2026, 03:44 PM UTC
Duration
—
Affected: DashboardAI Systems
Timeline · 6 updates
  1. investigating Jul 10, 2026, 04:46 PM UTC

    Status: Investigating We are aware of an issue affecting users being redirected to login screen and login attempts failing and are actively investigating. Affected components Dashboard (Full outage)

  2. investigating Jul 10, 2026, 04:57 PM UTC

    Status: Investigating Updating to include some AI systems like Pylon MCP are also impacted. An upstream vendor outage is being scoped as the potential root cause. https://status.launchdarkly.com/ Affected components Dashboard (Full outage) AI Systems (Partial outage)

  3. identified Jul 10, 2026, 05:20 PM UTC

    Status: Identified The upstream vendor has identified the issue and are implementing a fix. Login to the Pylon platform should no longer be impacted. Affected components Dashboard (Partial outage) AI Systems (Partial outage)

  4. identified Jul 10, 2026, 06:20 PM UTC

    Status: Identified The upstream vendor has resolved the root cause of the issue and are monitoring their systems. We are continuing to evaluate and monitor the impact to ensure full service is restored across all of our product areas. Affected components AI Systems (Partial outage) Dashboard (Partial outage)

  5. monitoring Jul 10, 2026, 06:26 PM UTC

    Status: Monitoring We are continuing to evaluate and monitor the impact to ensure full service is restored across all of our product areas. Affected components Dashboard (Partial outage) AI Systems (Partial outage)

  6. resolved Jul 12, 2026, 03:44 PM UTC

    Status: Resolved The issue has been resolved and all systems are operational. We will follow this update with a more detailed analysis and accurate timeline from our engineering team. Affected components Dashboard (Operational) AI Systems (Operational)

Read the full incident report →

Minor July 9, 2026

Pylon dashboard failing to load

Detected by Pingoru
Jul 09, 2026, 11:57 PM UTC
Resolved
Jul 09, 2026, 11:57 PM UTC
Duration
—
Affected: Dashboard
Timeline · 5 updates
  1. investigating Jul 09, 2026, 09:47 PM UTC

    Status: Investigating We are aware of an issue affecting slow loading or failure to load the Pylon dashboard and are actively investigating. Affected components Dashboard (Partial outage)

  2. identified Jul 09, 2026, 10:02 PM UTC

    Status: Identified We have identified the underlying cause of the issue and are working on a fix. Affected components Dashboard (Partial outage)

  3. identified Jul 09, 2026, 11:12 PM UTC

    Status: Identified The team is in the process of implementing a forward fix. The behavior experienced is scoped to slow dashboard/issue loading, delayed ingestion of issues, and some triggers related to issue creation and routing not initializing due to the delay. No data has been lost and we are currently processing the delayed queues. Thank you for your patience and please reach out to support with questions should you have any. Affected components Dashboard (Partial outage)

  4. monitoring Jul 09, 2026, 11:34 PM UTC

    Status: Monitoring We have implemented a fix and are monitoring our systems. Affected components Dashboard (Operational)

  5. resolved Jul 09, 2026, 11:57 PM UTC

    Status: Resolved The issue has been resolved and all systems are operational. Between approximately 2:41 PM and 2:53 PM PT, some customers experienced slow or failed dashboard loading. Dashboard availability recovered within approximately 12 minutes, but issue ingestion and related trigger processing remained delayed while we worked through the accumulated backlog. All delayed processing was caught up by 4:32 PM PT. We appreciate your patience while we addressed this issue. Should you have any follow up questions, please feel free to reach out to Support. Affected components Dashboard (Operational)

Read the full incident report →

Minor July 6, 2026

Inbound Email Delays

Detected by Pingoru
Jul 06, 2026, 10:28 PM UTC
Resolved
Jul 06, 2026, 10:28 PM UTC
Duration
—
Affected: Email
Timeline · 3 updates
  1. investigating Jul 06, 2026, 08:00 PM UTC

    Status: Investigating We are aware of an issue impacting US customer inbound email delays and are actively tracking. Our upstream vendor posted on their status page here. https://status.postmarkapp.com/notices/0rctfahtwuovx3ie-webhook-delays Affected components Email (Degraded performance)

  2. monitoring Jul 06, 2026, 10:10 PM UTC

    Status: Monitoring Our upstream provider identified the issue and deployed a fix. We will continue to monitor. Affected components Email (Operational)

  3. resolved Jul 06, 2026, 10:28 PM UTC

    Status: Resolved The issue has been resolved and all systems are operational. Affected components Email (Operational)

Read the full incident report →

Minor June 30, 2026

Knowledge Base content failing to load

Detected by Pingoru
Jun 30, 2026, 01:59 PM UTC
Resolved
Jun 30, 2026, 01:59 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Jun 30, 2026, 01:40 PM UTC

    Status: Investigating We are aware of an issue affecting some Knowledge Base articles failing to load and are actively investigating.

  2. monitoring Jun 30, 2026, 01:45 PM UTC

    Status: Monitoring Our engineers implemented a rollback and affected articles are now loading as expected. We are continuing to monitor our systems.

  3. resolved Jun 30, 2026, 01:59 PM UTC

    Status: Resolved The issue has been resolved and all systems are operational. Please reach out to Support if you continue to have issues.

Read the full incident report →

Minor June 24, 2026

API Latency

Detected by Pingoru
Jun 24, 2026, 03:06 PM UTC
Resolved
Jun 24, 2026, 03:06 PM UTC
Duration
—
Affected: API
Timeline · 4 updates
  1. investigating Jun 24, 2026, 02:30 PM UTC

    Status: Investigating We are aware of an issue affecting some latency with API calls and are actively investigating. Affected components API (Degraded performance)

  2. identified Jun 24, 2026, 02:40 PM UTC

    Status: Identified We have identified the underlying cause of the latency on the API and are working on a fix. Affected components API (Degraded performance)

  3. monitoring Jun 24, 2026, 02:56 PM UTC

    Status: Monitoring Our engineers have implemented a fix and are monitoring our systems. Affected components API (Degraded performance)

  4. resolved Jun 24, 2026, 03:06 PM UTC

    Status: Resolved The issue has been resolved and all systems are operational- thank you for your pateince and we apologize for any disruption to your workflows. Affected components API (Operational)

Read the full incident report →

Minor June 12, 2026

WhatsApp integration errors

Detected by Pingoru
Jun 12, 2026, 03:15 PM UTC
Resolved
Jun 12, 2026, 03:15 PM UTC
Duration
—
Affected: Chat & Messaging
Timeline · 3 updates
  1. investigating Jun 12, 2026, 02:12 PM UTC

    Status: Investigating We are aware of an issue affecting Whatsapp source issues and are actively investigating. Affected components Chat & Messaging (Degraded performance)

  2. monitoring Jun 12, 2026, 02:35 PM UTC

    Status: 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. Affected components Chat & Messaging (Operational)

  3. resolved Jun 12, 2026, 03:15 PM UTC

    Status: 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. Affected components Chat & Messaging (Operational)

Read the full incident report →

Minor June 11, 2026

Delays in broadcast sending

Detected by Pingoru
Jun 11, 2026, 04:20 PM UTC
Resolved
Jun 11, 2026, 04:20 PM UTC
Duration
—
Affected: Broadcasts
Timeline · 2 updates
  1. investigating Jun 11, 2026, 03:49 PM UTC

    Status: Investigating Our engineering team is investigating an issue causing delays in the sending of broadcasts. We will post updates here as soon as they are available. We apologize for any impact this is having on your operations, please reach out to Pylon support with any questions. Affected components Broadcasts (Degraded performance)

  2. resolved Jun 11, 2026, 04:20 PM UTC

    Status: Resolved Our engineering team has rolled out a fix for the underlying issue and we have confirmed this is now fully resolved. We apologize for any impact this had on your operation, please reach out to Pylon support with any questions. Affected components Broadcasts (Operational)

Read the full incident report →

Minor June 9, 2026

Delay in analytics data

Detected by Pingoru
Jun 09, 2026, 04:40 AM UTC
Resolved
Jun 09, 2026, 04:40 AM UTC
Duration
—
Affected: Analytics
Timeline · 2 updates
  1. monitoring Jun 08, 2026, 11:22 PM UTC

    Status: Monitoring Our engineering team has identified an issue causing a delay in data availability in analytics and rolled out a fix. Analytics data is currently catching up and is roughly 90 minutes behind. We are monitoring and will post an update here once we have confirmed it is fully resolved. Affected components Analytics (Degraded performance)

  2. resolved Jun 09, 2026, 04:40 AM UTC

    Status: Resolved Our engineering team has confirmed this is now fully resolved, analytics data is fully caught up. We apologize for any impact this had on your operation, please reach out to Pylon support with any questions. Affected components Analytics (Operational)

Read the full incident report →

Minor June 5, 2026

Delays in outbound email delivery

Detected by Pingoru
Jun 05, 2026, 04:14 AM UTC
Resolved
Jun 05, 2026, 04:14 AM UTC
Duration
—
Affected: Email
Timeline · 2 updates
  1. monitoring Jun 04, 2026, 11:39 PM UTC

    Status: 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 Affected components Email (Degraded performance)

  2. resolved Jun 05, 2026, 04:14 AM UTC

    Status: Resolved The issue has been resolved and all systems are operational. Affected components Email (Operational)

Read the full incident report →

Minor May 29, 2026

Delay in data availability in analytics

Detected by Pingoru
May 29, 2026, 03:49 PM UTC
Resolved
May 29, 2026, 03:49 PM UTC
Duration
—
Affected: Analytics
Timeline · 2 updates
  1. investigating May 29, 2026, 12:52 AM UTC

    Status: Investigating Our engineering team is investigating an issue causing roughly a 2 hour delay in data availability in Analytics. We will post updates here as more information becomes available. Please reach out to Pylon support with any questions. Affected components Analytics (Degraded performance)

  2. resolved May 29, 2026, 03:49 PM UTC

    Status: Resolved Our engineering team has rolled out a fix for the underlying issue and analytics data is now fully caught up. We apologize for any impact this had on your operation, please reach out to Pylon support with any questions. Affected components Analytics (Operational)

Read the full incident report →

Minor May 28, 2026

Slack service latency

Detected by Pingoru
May 28, 2026, 03:45 PM UTC
Resolved
May 28, 2026, 03:45 PM UTC
Duration
—
Affected: Chat & Messaging
Timeline · 2 updates
  1. identified May 27, 2026, 11:11 PM UTC

    Status: Identified Slack is experiencing an incident: https://slack-status.com/2026-05/fd9a431182c72eeb 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. Affected components Chat & Messaging (Degraded performance)

  2. resolved May 28, 2026, 03:45 PM UTC

    Status: 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. Affected components Chat & Messaging (Operational)

Read the full incident report →

Minor May 26, 2026

Delays in scheduled event processing

Detected by Pingoru
May 26, 2026, 06:45 PM UTC
Resolved
May 26, 2026, 06:45 PM UTC
Duration
—
Affected: Data WarehouseTriggers & WorkflowsBroadcasts
Timeline · 4 updates
  1. investigating May 26, 2026, 06:07 PM UTC

    Status: 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. Affected components Triggers & Workflows (Degraded performance) Broadcasts (Degraded performance)

  2. identified May 26, 2026, 06:16 PM UTC

    Status: 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. Affected components Data Warehouse (Degraded performance) Broadcasts (Degraded performance) Triggers & Workflows (Degraded performance)

  3. monitoring May 26, 2026, 06:32 PM UTC

    Status: 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. Affected components Broadcasts (Operational) Triggers & Workflows (Operational) Data Warehouse (Operational)

  4. resolved May 26, 2026, 06:45 PM UTC

    Status: 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. Affected components Triggers & Workflows (Operational) Data Warehouse (Operational) Broadcasts (Operational)

Read the full incident report →

Minor May 14, 2026

Slack Related Errors

Detected by Pingoru
May 14, 2026, 03:53 PM UTC
Resolved
May 14, 2026, 03:53 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 14, 2026, 03:06 PM UTC

    Status: Investigating We are aware of an issue affecting Slack issue reactions, image uploads, and message editing. Tracking on the Slack Status Page here: https://slack-status.com/2026-05/fe557ca05fdb64fa!

  2. identified May 14, 2026, 03:22 PM UTC

    Status: Identified Slack has reported: https://slack-status.com/2026-05/fe557ca05fdb64fa that they have identified the underlying issue and are working on a configuration change.

  3. monitoring May 14, 2026, 03:37 PM UTC

    Status: Monitoring Slack has implemented a fix: https://slack-status.com/2026-05/fe557ca05fdb64fa and has Resolved their incident- we will continue to monitor on our end. The deployed fix will require a hard refresh of your Slack app/browser.

  4. resolved May 14, 2026, 03:53 PM UTC

    Status: Resolved The Slack issue and status page have been resolved and all systems are operational.

Read the full incident report →

Minor May 5, 2026

Analytics Dashboards Delay

Detected by Pingoru
May 05, 2026, 12:43 AM UTC
Resolved
May 05, 2026, 12:43 AM UTC
Duration
—
Affected: Analytics
Timeline · 4 updates
  1. investigating May 04, 2026, 01:47 PM UTC

    Status: Investigating We are aware of an issue affecting Analytics Dashboards delays and are actively investigating. Affected components Analytics (Degraded performance)

  2. identified May 04, 2026, 03:28 PM UTC

    Status: Identified We have identified the underlying cause of the delayed analytics issue and are working on a fix. Affected components Analytics (Degraded performance)

  3. monitoring May 04, 2026, 04:49 PM UTC

    Status: Monitoring We have implemented a fix and are monitoring as the data is being updated. Affected components Analytics (Degraded performance)

  4. resolved May 05, 2026, 12:43 AM UTC

    Status: Resolved The underlying issue has been resolved and analytics data has been fully backfilled. We appreciate your patience while we worked to resolve this, please reach out to Pylon support with any questions. Affected components Analytics (Operational)

Read the full incident report →

Minor April 9, 2026

Inbound email message delays

Detected by Pingoru
Apr 09, 2026, 01:36 AM UTC
Resolved
Apr 09, 2026, 01:36 AM UTC
Duration
—
Affected: Email
Timeline · 4 updates
  1. identified Apr 08, 2026, 04:28 PM UTC

    Status: Identified Our team has identified an issue with our mail service provider causing delays in receiving some inbound email messages and are working with them towards a resolution. We apologize for any impact this may have on your operations, we will post updates here as soon as they are available. Please reach out to Pylon support with any questions. Affected components Email (Degraded performance)

  2. identified Apr 08, 2026, 08:13 PM UTC

    Status: Identified Our engineering team is continuing to investigate this issue and it appears to be related to a Gmail incident: https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT beginning at 6:30 am PDT. The Gmail team is working on mitigation steps but does not have an expected ETA for a fix at this time. We will post further updates here as soon as they are available. Affected components Email (Degraded performance)

  3. monitoring Apr 08, 2026, 11:38 PM UTC

    Status: Monitoring Google has announced that they have mitigated and resolved the incident: https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT causing delays in sending and receiving messages. We are currently seeing emails that were impacted by the delay hitting our servers successfully. We will continue monitoring our mail servers until we are satisfied that all emails are coming in in real time once again. We appreciate your patience while this was ongoing and sincerely apologize for any impact this had on your operations. Please reach out to Pylon support with any questions. Affected components Email (Operational)

  4. resolved Apr 09, 2026, 01:36 AM UTC

    Status: Resolved Our team has been closely monitoring our inbound mail server since Google resolved their incident and have confirmed messages are again consistently arriving in real time. We are considering this resolved - thank you for your patience while this was ongoing and please reach out to Pylon support with any questions. Affected components Email (Operational)

Read the full incident report →

Minor April 7, 2026

Delay in data availability in Analytics

Detected by Pingoru
Apr 07, 2026, 10:49 PM UTC
Resolved
Apr 07, 2026, 10:49 PM UTC
Duration
—
Affected: Dashboard
Timeline · 3 updates
  1. identified Apr 03, 2026, 07:54 PM UTC

    Status: Identified Our engineering team has identified an issue causing a delay in data availability in Analytics and is working on a fix. We apologize for any impact this is having on your operations and will post updates here as soon as they are available. Please reach out to Pylon support with any questions. Affected components Dashboard (Degraded performance)

  2. identified Apr 07, 2026, 04:44 PM UTC

    Status: Identified Our engineering team is continuing to actively work towards a resolution with our vendor. We understand the impact this may have on your operations and apologize for the continued delay in data availability, we do not anticipate any data loss as a result. We will post updates here as soon as they are available, please reach out to Pylon support with any questions. Affected components Dashboard (Degraded performance)

  3. resolved Apr 07, 2026, 10:49 PM UTC

    Status: Resolved Our engineering team has rolled out a fix for the underlying issue and recent analytics data should again be displaying as expected. We appreciate your patience while we worked to address this, please reach out to Pylon support with any questions. Affected components Dashboard (Operational)

Read the full incident report →

Minor April 4, 2026

Platform loading issues

Detected by Pingoru
Apr 04, 2026, 12:39 AM UTC
Resolved
Apr 04, 2026, 12:39 AM UTC
Duration
—
Affected: Dashboard
Timeline · 3 updates
  1. monitoring Apr 03, 2026, 11:54 PM UTC

    Status: Monitoring Our engineering team has identified an issue causing slow loading within the platform and is working on a fix. We will post updates here as soon as they are available. We apologize for any impact this is having on your operations and please reach out to Pylon support with any questions. Affected components Dashboard (Degraded performance)

  2. identified Apr 03, 2026, 11:56 PM UTC

    Status: Identified Our engineering team has identified an issue causing slow loading within the platform and is working on a fix. We will post updates here as soon as they are available. We apologize for any impact this is having on your operations and please reach out to Pylon support with any questions. Affected components Dashboard (Degraded performance)

  3. resolved Apr 04, 2026, 12:39 AM UTC

    Status: Resolved Our engineering team has rolled out a fix and the platform loading issues have been resolved. We appreciate your patience while we worked to address this and apologize for any impact this had on your operations. Please reach out to Pylon support with any questions. Affected components Dashboard (Operational)

Read the full incident report →

Minor March 30, 2026

Email deliverability issues

Detected by Pingoru
Mar 30, 2026, 07:50 PM UTC
Resolved
Mar 30, 2026, 07:50 PM UTC
Duration
—
Affected: Chat & Messaging
Timeline · 3 updates
  1. identified Mar 27, 2026, 05:17 PM UTC

    Status: Identified Our engineering team has identified an issue with our mail service provider that is causing some emails to appear as sent in Pylon but not successfully deliver. We have escalated this with our vendor and are working towards a resolution. We apologize for any impact this is having on your operations and we will post additional updates here as soon as we have more information. Affected components Chat & Messaging (Degraded performance)

  2. monitoring Mar 28, 2026, 12:55 AM UTC

    Status: Monitoring Our engineering team has rolled out a change to mitigate this behavior and allows for all emails to again reliably send from Pylon. We are still waiting for confirmation from our vendor that the underlying cause on their end has been fixed before calling this fully resolved. We will post an additional update here once that is confirmed. We appreciate your patience while we were working on a fix, please reach out to Pylon support with any questions. Affected components Chat & Messaging (Operational)

  3. resolved Mar 30, 2026, 07:50 PM UTC

    Status: Resolved We have received confirmation from our mail service provider that the underlying issue has been fixed on their end as well and this is now fully resolved going forward. We apologize for any impact this had on your operations, please reach out to Pylon support with any additional questions. Affected components Chat & Messaging (Operational)

Read the full incident report →