# Slack service latency

- Provider: [Pylon](https://down.guide/pylon)
- Level: confirmed
- Impact: Degraded
- lasted 16h 34m
- started 2026-05-27 23:11 UTC
- id: DWN-9364790f25
- Official page: https://status.usepylon.com/incidents/01KSNVAXDYEBACDRC9BF5DP3ZY

## Updates from Pylon
### 2026-05-27 23:11 UTC: identified
Slack is experiencing \[an incident\](https://slack-status.com/2026-05-27) 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.

### 2026-05-28 15:45 UTC: 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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).