Pylon incident

Slack Integration Connection Issues

Ongoing since 03:52 PM UTC, affecting Integrations (Product Ticketing).

monitoring Nov 11, 2026, 04:30 PM UTC

We’re seeing signs of recovery for Slack integration connectivity, though Slack is still reporting impact across several areas, including Connectivity, Messaging, Apps/Integrations/APIs, and Workspace/Org Administration. You may still encounter intermittent issues while Slack continues recovering. We recommend continuing to monitor Slack’s status page for the latest updates and confirmation of full recovery: https://slack-status.com/2026-11/b8bb993128ac94f5. We’ll also continue monitoring and will share another update once we’ve confirmed the issue is fully resolved.

Started
Nov 11, 2026, 03:52 PM UTC
Resolved
Ongoing
Duration
● 59m
Detected by Pingoru
Nov 11, 2026, 03:52 PM UTC

Affected components

Integrations (Product Ticketing)

Update timeline

  1. investigating Nov 11, 2026, 03:52 PM UTC

    We’re investigating reports of Slack integrations appearing disconnected or inactive in Pylon. Some customers may see prompts to reauthorize Slack, “Unable to connect to Slack” messages, or Slack integrations showing as inactive even after reauthorization. This appears to be related to an active Slack-side service disruption, and we expect affected Pylon Slack integrations to recover once Slack services stabilize. We’re continuing to monitor Slack’s status and will update this page as we learn more. Customers can also follow Slack’s status page here: https://slack-status.com/

  2. monitoring Nov 11, 2026, 04:30 PM UTC

    We’re seeing signs of recovery for Slack integration connectivity, though Slack is still reporting impact across several areas, including Connectivity, Messaging, Apps/Integrations/APIs, and Workspace/Org Administration. You may still encounter intermittent issues while Slack continues recovering. We recommend continuing to monitor Slack’s status page for the latest updates and confirmation of full recovery: https://slack-status.com/2026-11/b8bb993128ac94f5. We’ll also continue monitoring and will share another update once we’ve confirmed the issue is fully resolved.

Your product runs on more than Pylon

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →