{
  "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, Discord, webhook, and email outage alerts across your vendor stack."
      }
    },
    "generatedAt": "2026-07-24T17:35:11.564Z"
  },
  "data": {
    "id": "incident_statuspage_imperva_l870hl392w1q",
    "slug": "imperva-inc-1002-johannesburg-south-africa-qra-data-center-issue-2026-03-27",
    "title": "[INC-1002] Johannesburg, South Africa (QRA) Data Center Issue",
    "summary": "[INC-1002] Johannesburg, South Africa (QRA) Data Center Issue",
    "status": "resolved",
    "severity": "major",
    "startedAt": "2026-03-27T12:23:40.431+00:00",
    "updatedAt": "2026-03-27T13:32:52.098+00:00",
    "resolvedAt": "2026-03-27T13:32:52.079+00:00",
    "provider": {
      "slug": "imperva",
      "name": "Imperva"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/imperva-inc-1002-johannesburg-south-africa-qra-data-center-issue-2026-03-27",
      "api": "/api/v1/incidents/imperva-inc-1002-johannesburg-south-africa-qra-data-center-issue-2026-03-27",
      "providerHtml": "/providers/imperva"
    },
    "impactSummary": "Imperva reported a major event for the affected tracked services.",
    "source": {
      "id": "source_imperva_status",
      "kind": "official_api",
      "name": "Imperva Status",
      "checkedAt": "2026-07-24T17:25:04.235+00:00",
      "officialUrl": "https://status.imperva.com",
      "statusPageUrl": "https://status.imperva.com"
    },
    "updates": [
      {
        "id": "update_statuspage_imperva_l870hl392w1q_z0x97py7jw72",
        "status": "investigating",
        "body": "Technical teams are investigating a potential issue in the Johannesburg, South Africa (QRA) data center. Further updates to follow.\n\nThe status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.\n \nIn the event of a service disruption, the update will include potential impacts to any affected region.",
        "createdAt": "2026-03-27T12:23:40.561+00:00"
      },
      {
        "id": "update_statuspage_imperva_l870hl392w1q_8p9zr4k666gl",
        "status": "monitoring",
        "body": "A fix has been implemented, and the issue has been mitigated. We are continuing to monitor in order to ensure that service has returned to normal.\n\nThe status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.\n \nIn the event of a service disruption, the update will include potential impacts to any affected region.",
        "createdAt": "2026-03-27T12:32:27.12+00:00"
      },
      {
        "id": "update_statuspage_imperva_l870hl392w1q_p90nbvpgnfg1",
        "status": "resolved",
        "body": "Some customer traffic being processed in Johannesburg, South Africa (QRA) PoP may have experienced higher than expected latency and packet loss due to an upstream provider issue, outside of the Thales Imperva Network. \nEngineers bypassed two impacted circuits in order to remove them from production, resulting in stabilized traffic. Services are now stable. Additional details will be provided following a completed root cause analysis.",
        "createdAt": "2026-03-27T13:32:52.079+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}