{
  "meta": {
    "version": "v1",
    "pricing": {
      "public": {
        "label": "Public",
        "description": "Read-only API access for lightweight status checks and public integrations."
      },
      "premium": {
        "label": "Premium",
        "description": "API keys with higher hourly quotas, plus Slack, Teams, Discord, webhook, and email outage alerts across your vendor stack."
      }
    },
    "generatedAt": "2026-10-23T02:59:08.839Z"
  },
  "data": {
    "id": "incident_slack_1582",
    "slug": "slack-slack-real-time-connection-disruption-2026-10-22",
    "title": "Slack Real-Time Connection Disruption",
    "summary": "Slack Real-Time Connection Disruption",
    "status": "resolved",
    "stale": false,
    "severity": "major",
    "startedAt": "2026-10-22T18:50:50+00:00",
    "updatedAt": "2026-10-22T18:50:50+00:00",
    "resolvedAt": "2026-10-22T18:50:50+00:00",
    "provider": {
      "slug": "slack",
      "name": "Slack"
    },
    "affectedServices": [
      {
        "slug": "slack-messaging",
        "name": "Messaging"
      }
    ],
    "links": {
      "html": "/incidents/slack-slack-real-time-connection-disruption-2026-10-22",
      "api": "/api/v1/incidents/slack-slack-real-time-connection-disruption-2026-10-22",
      "providerHtml": "/providers/slack",
      "alerts": "https://outagedeck.com/account?stack=slack&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "Slack reported an incident affecting Messaging.",
    "source": {
      "id": "source_slack_status",
      "kind": "official_api",
      "name": "Slack System Status",
      "checkedAt": "2026-10-23T02:50:12.765+00:00",
      "stale": false,
      "officialUrl": "https://slack-status.com",
      "statusPageUrl": "https://slack-status.com"
    },
    "updates": [
      {
        "id": "update_slack_1582_20261022t1150500700",
        "status": "resolved",
        "body": "Some Slack customers experienced disrupted real-time connections, delayed message delivery, and errors loading conversation history on October 22, 2026, starting at 16:08 UTC. A large number of active connections closed at once and then reconnected, which briefly strained the services customers rely on to send and read messages. By 16:26 UTC, connections had reconnected and service had returned to normal. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.",
        "createdAt": "2026-10-22T18:50:50+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}