{
  "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-09-04T22:17:02.434Z"
  },
  "data": {
    "id": "incident_statuspage_proton_lj22kf1nc8yz",
    "slug": "proton-service-disruption-2026-09-01",
    "title": "Service disruption",
    "summary": "Service disruption",
    "status": "resolved",
    "severity": "major",
    "startedAt": "2026-09-01T14:42:09+00:00",
    "updatedAt": "2026-09-01T21:42:23.404+00:00",
    "resolvedAt": "2026-09-01T18:49:51+00:00",
    "provider": {
      "slug": "proton",
      "name": "Proton"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/proton-service-disruption-2026-09-01",
      "api": "/api/v1/incidents/proton-service-disruption-2026-09-01",
      "providerHtml": "/providers/proton",
      "alerts": "https://outagedeck.com/account?stack=proton&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "Proton reported a major event for the affected tracked services.",
    "source": {
      "id": "source_proton_status",
      "kind": "official_api",
      "name": "Proton Status",
      "checkedAt": "2026-09-04T22:15:03.853+00:00",
      "officialUrl": "https://status.proton.me",
      "statusPageUrl": "https://status.proton.me"
    },
    "updates": [
      {
        "id": "update_statuspage_proton_lj22kf1nc8yz_63c8psdn860s",
        "status": "investigating",
        "body": "We’re aware that a small number of users may be experiencing issues accessing Proton services.\nOur team is investigating and we will share updates here as soon as possible.\nWe apologize for the inconvenience.",
        "createdAt": "2026-09-01T12:37:58.835+00:00"
      },
      {
        "id": "update_statuspage_proton_lj22kf1nc8yz_bmwr9npylhkm",
        "status": "investigating",
        "body": "We are currently dealing with residual hardware failures that are likely related to the damage suffered from the overheating incident last week. At the moment we are operating at a reduced capacity, while our engineers work to bring additional infrastructure online. We apologize for the unfortunate timing of this incident and any disruption or inconvenience this may have caused you.",
        "createdAt": "2026-09-01T14:42:09.759+00:00"
      },
      {
        "id": "update_statuspage_proton_lj22kf1nc8yz_sn3nfb1fyv68",
        "status": "identified",
        "body": "Database capacity is being restored. Traffic limitations are being gradually lifted and outgoing mail will be re-enabled as soon as the situation is stable. Queued emails will be delivered progressively, and no data was lost as a result of this disruption.\n\nThank you for your patience, we'll update you again once everything is back to normal.",
        "createdAt": "2026-09-01T17:10:07.458+00:00"
      },
      {
        "id": "update_statuspage_proton_lj22kf1nc8yz_f0f543dz3v77",
        "status": "monitoring",
        "body": "Traffic limitations have been fully removed for all users.\n\nServices are returning to normal operation, and outgoing mail will be gradually re-enabled in 15 minutes. Messages that were queued during the disruption are being delivered progressively\n\nOur engineers continue to monitor the infrastructure closely as capacity returns to full levels.\n\nWe'll confirm here once everything is completely back to normal.",
        "createdAt": "2026-09-01T17:26:18.342+00:00"
      },
      {
        "id": "update_statuspage_proton_lj22kf1nc8yz_6mfb7304llpm",
        "status": "resolved",
        "body": "UPDATE:\nThe incident recovery caused some push notifications related to suspicious login activity to be delivered several hours later than expected.\n\nThe delay affected only the delivery of these notifications and was related to the service disruption experienced earlier today. The delayed notifications have now been processed, and the system has returned to normal operation.\n\nWe apologize for any confusion this may have caused.\n---\nEarlier today, a subset of Proton users experienced intermittent service disruptions.\n\nThe incident began during exceptional database maintenance following last week's datacenter overheating incident. The maintenance had been tested and was expected to cause only a brief disruption.\n\nHowever, the switchover exposed additional instability under high load, and this forced us to remove some additional infrastructure from service and operate at reduced capacity for a time.\n\nWe have now stabilized all Proton services and all are currently operational. No user data has been lost. We apologize for the disruption.",
        "createdAt": "2026-09-01T18:49:51.028+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}