{
  "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-23T14:00:31.270Z"
  },
  "data": {
    "id": "incident_statuspage_keeper_v7ms88h489fd",
    "slug": "keeper-api-errors-during-maintenance-operation-2026-03-31",
    "title": "API errors during maintenance operation",
    "summary": "API errors during maintenance operation",
    "status": "resolved",
    "severity": "major",
    "startedAt": "2026-04-01T01:40:37.77+00:00",
    "updatedAt": "2026-04-01T01:41:16.08+00:00",
    "resolvedAt": "2026-03-31T03:00:00+00:00",
    "provider": {
      "slug": "keeper",
      "name": "Keeper Security"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/keeper-api-errors-during-maintenance-operation-2026-03-31",
      "api": "/api/v1/incidents/keeper-api-errors-during-maintenance-operation-2026-03-31",
      "providerHtml": "/providers/keeper"
    },
    "impactSummary": "Keeper Security reported a major event for the affected tracked services.",
    "source": {
      "id": "source_keeper_status",
      "kind": "official_api",
      "name": "Keeper Status",
      "checkedAt": "2026-07-23T13:55:03.383+00:00",
      "officialUrl": "https://statuspage.keeper.io",
      "statusPageUrl": "https://statuspage.keeper.io"
    },
    "updates": [
      {
        "id": "update_statuspage_keeper_v7ms88h489fd_69s4sbb6q62l",
        "status": "resolved",
        "body": "On March 30 at 8:00 PM PST, Keeper performed a scheduled minor upgrade to our multi-region AWS RDS clusters as part of routine maintenance. The upgrade itself completed in approximately 3 minutes, followed by a standard application restart process that took about 15 minutes. While this process is typically non-disruptive, recent changes to service health checks caused unexpected customer impact during the restart window.\n\nThis maintenance was not communicated in advance due to an internal miscommunication and the expectation of no impact. We apologize for the disruption and are taking steps to ensure all future maintenance—regardless of expected impact—is communicated ahead of time, as well as reviewing our health check configurations to prevent similar issues.",
        "createdAt": "2026-04-01T01:40:37.819+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}