{
  "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-21T20:14:45.045Z"
  },
  "data": {
    "id": "incident_statuspage_check-point_s1qngsgdrkzj",
    "slug": "check-point-eu-data-ingestion-disruption-june-29-30-2026-2026-07-01",
    "title": "EU Data Ingestion Disruption - June 29-30, 2026",
    "summary": "EU Data Ingestion Disruption - June 29-30, 2026",
    "status": "resolved",
    "stale": false,
    "severity": "minor",
    "startedAt": "2026-06-29T08:00:00+00:00",
    "updatedAt": "2026-07-01T11:03:01.626+00:00",
    "resolvedAt": "2026-06-29T08:00:00+00:00",
    "provider": {
      "slug": "check-point",
      "name": "Check Point"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/check-point-eu-data-ingestion-disruption-june-29-30-2026-2026-07-01",
      "api": "/api/v1/incidents/check-point-eu-data-ingestion-disruption-june-29-30-2026-2026-07-01",
      "providerHtml": "/providers/check-point",
      "alerts": "https://outagedeck.com/account?stack=check-point&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "Check Point reported a minor event for the affected tracked services.",
    "source": {
      "id": "source_check_point_status",
      "kind": "official_api",
      "name": "Check Point Status",
      "checkedAt": "2026-10-21T20:10:57.07+00:00",
      "stale": false,
      "officialUrl": "https://status.checkpoint.com",
      "statusPageUrl": "https://status.checkpoint.com"
    },
    "updates": [
      {
        "id": "update_statuspage_check-point_s1qngsgdrkzj_3t02yc209rxy",
        "status": "resolved",
        "body": "Incident Duration: June 29, 08:00 UTC – June 30, 09:30 UTC (~26 hours)\nAffected Services: Datatube EU Production - West Europe region\nAffected Products: CloudGuard WAF, Playblocks, XDR\n \n────────────────────────────\n \nOverview\n \nOn June 29–30, 2026, EU production Datatube services experienced a partial degradation affecting data ingestion in the West Europe region, a small portion of events experienced delayed processing during this window. \n \n────────────────────────────\n \nCustomer Impact\n \nDuring the incident window, approximately ~0.2% of total EU ingestion events were affected across products.\n \nCustomers using CloudGuard WAF, Playblocks, or XDR in the West Europe region may have experienced:\n- Delayed visibility of security events in dashboards and reports\n- Delayed data in queries covering the June 29–30 window\n \n────────────────────────────\n \nIncident Timeline (UTC)\n \nJun 29 – 08:00   First customer reports received; investigation initiated immediately, cross-team investigation mobilized across infrastructure, networking, and product teams.\n \nJun 29 – 10:00   First mitigation applied - provided temporary partial relief.\n \nJun 29 – 13:30   Second mitigation applied, narrowing the root cause scope further, also provided temporary partial relief.\n \nJun 29 – 18:00   Issue confirmed as affecting multiple products; joint investigation continued.\n \nJun 29 – 21:15   Capacity expanded to stabilize the environment and protect against further degradation.\n \nJun 30 – 05:00   Final diagnostic steps executed to isolate root cause precisely.\n \nJun 30 – 09:30   Root cause confirmed and resolved; all services fully restored.\n \nThe investigation required coordinated effort across multiple teams because early symptoms were consistent with several possible root causes. Each mitigation step both provided partial relief and helped narrow the diagnosis - this is standard practice to avoid introducing new risk while a production system is under stress.\n \n────────────────────────────\n \nRoot Cause\n \nA misconfiguration in the EU gateway's communication protocols, which was dormant under normal operating conditions, was triggered by load introduced during routine maintenance. Once identified, the fix was straightforward and immediately effective.\n \n────────────────────────────\n \nNext Steps & Action Items\n \n1. Audit and align protocol configurations across all regional gateways - to prevent recurrence in other regions.\n2. Add capacity alerting on all regional gateways - to detect such anomalies before they cause customer impact.\n3. Improve client-side monitoring to surface connection-level failures and latencies earlier.\n4. Introduce stress testing for sensitive network components as part of the change process - validating configurations in an isolated, production-like environment before and after any change to catch hidden issues before they reach production.",
        "createdAt": "2026-07-01T11:00:18.975+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}