Pylon Outage History

A Slack service issue affected reactions, image uploads, and message editing functionality for 47 minutes. Slack identified the underlying problem and implemented a configuration fix that required users to perform a hard refresh of their Slack app or browser. The incident was resolved and monitoring continued to ensure stability.

Pylon experienced a service incident where analytics dashboards failed to load properly for 2.9 hours. The engineering team identified the underlying issue and worked on implementing a fix. The incident has been resolved, restoring normal dashboard functionality.

Pylon's Analytics Dashboards experienced delays for 11 hours, preventing users from accessing up-to-date analytics data. The team identified the underlying cause and implemented a fix, with monitoring in place as the data updates were restored.

Pylon experienced a 9.2-hour service incident where inbound email messages were delayed due to an issue with their mail service provider, which was later identified as a Gmail incident affecting message sending and receiving. The issue was resolved when Google mitigated their incident, allowing delayed emails to successfully reach Pylon's servers. Pylon continued monitoring their mail servers to ensure real-time email delivery was fully restored.

Pylon experienced slow loading issues affecting the Dashboard component for 47 minutes. The engineering team identified and worked on a fix for the platform performance problem. The issue was resolved after monitoring and implementing the necessary corrections.

Pylon's Analytics service experienced a delay in data availability that affected the Dashboard component for 99 hours. The engineering team identified the issue and worked with a vendor on a resolution. No data loss was anticipated during the incident.

Pylon experienced email deliverability issues caused by their mail service provider, where emails appeared as sent within Pylon but failed to actually deliver to recipients. The issue affected the Integrations component and lasted 74.6 hours. The engineering team implemented a mitigation that restored reliable email sending from Pylon while continuing to work with their vendor on the underlying fix.

Pylon's Customer Portal experienced login failures that prevented users from accessing the Dashboard for 19 minutes. The engineering team investigated the issue and deployed a fix. The service was restored and is being monitored to ensure full resolution.

Pylon experienced a 3.2-hour service incident where some users were unable to login using Slack authentication. The engineering team identified the issue as originating from Slack's authentication system and escalated it to the Slack team. The incident was resolved when successful Slack logins resumed, with the team continuing to monitor the system.

The Pylon platform experienced loading issues that prevented pages on app.usepylon.com from loading for some organizations, affecting the Dashboard, Integrations, and API components. The engineering team identified the root cause and deployed a fix within 1.5 hours. The team continued monitoring the platform and worked on additional remediation steps to ensure full resolution.