Is Pylon Down?

The upstream Anthropic incident affecting Claude connectors has been resolved (<https://status.claude.com/incidents/34wq7gxnxvvm>). The Pylon connector in Claude has been working normally since ~ 15:00 UTC. From about 13:05 UTC, many customers saw the Pylon connector in Claude fail or respond slowly. Any scheduled automations that rely on the connector may need to be re-run. If you still have problems with the Pylon connector in Claude, try reconnecting it in Claude under Settings → Connectors. --- [2026-11-13T14:47:03Z] (monitoring) We're aware that the Pylon connector in Claude is failing or responding slowly for many customers since about 13:05 UTC. This comes from an ongoing incident at Anthropic that affects Claude connectors: <https://status.claude.com/incidents/34wq7gxnxvvm>. Pylon's own services, including the Pylon app, API and MCP server, are working normally. Anthropic reports partial recovery, and we're seeing connector traffic start to come back. We'll keep monitoring and post an update when the connector is fully restored.

We are seeing significant recovery from Microsoft’s incident (MO1550821). Since approximately 12:00 UTC today, Outlook Email events for our US region are processing normally again, and replies sent through connected Outlook mailboxes are going out. Event processing for our EU region has also fully recovered as of ~13:30 UTC today. Our engineering team is working to reprocess events that were dropped during the incident window and we will post another update once that is complete. Please reach out to Pylon support with any questions. --- [2026-11-12T22:42:05Z] (identified) Microsoft is continuing to work on their incident (MO1550821) affecting Outlook Email, Calendar, and Teams, which is causing delayed and failed event processing. Our engineering team has deployed mitigations on our end to reduce the impact while the incident is ongoing, and we continue to monitor closely. Once Microsoft resolves the incident, we will run a recovery process to backfill any Outlook Email and Calendar events missed during the outage window. We will post updates here as soon as they are available. We apologize for any impact this is having on your operation, please reach out to Pylon support with any questions. --- [2026-11-12T19:13:32Z] (identified) Microsoft is experiencing an incident (MO1550821) affecting Outlook Email, Calendar, and Teams causing delayed and failed event processing. They are actively working on a fix and our engineering team is closely monitoring. We will post updates here as soon as they are available. We apologize for any impact this is having on your operation, please reach out to Pylon support with any questions.

Slack has confirmed the [incident](https://slack-status.com/2026-11/b8bb993128ac94f5) is fully resolved on their end, please reach out to Pylon support with any questions. --- [2026-11-11T17:30:53Z] (monitoring) Our engineering team has confirmed the Pylon <> Slack integration is fully functional, we are closely monitoring and will post a final update once Slack resolves their incident. During the incident window, message ingestion was unaffected, messages sent from Pylon to Slack may have had a small delay before sending. Some Slack DM notifications sent by Pylon between 14:55–15:22 UTC were also affected. Users may have seen the Slack integration as unhealthy within Pylon. We apologize for any impact this had on your operation, please reach out to Pylon support with any questions. --- [2026-11-11T16:30:10Z] (monitoring) 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. --- [2026-11-11T15:52:52Z] (investigating) 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/>