Region - Down incident at 2026-02-16 19:08

critical RESOLVED

Affected Service

Region

Started

Feb 16, 2026 19:08 UTC

Resolved

Feb 16, 2026 20:28 UTC

Duration

1.3 hours

Feb 16, 2026 20:28 UTC System

Monitor is back up. Incident resolved automatically.

Feb 16, 2026 20:24 UTC System

Incident reopened: Monitor detected as down again. Location: uk-lon-1 Cause: Unexpected status code: got 200, expected one of [202]

Feb 16, 2026 20:15 UTC System

Monitor is back up. Incident resolved automatically.

Feb 16, 2026 20:09 UTC System

Incident reopened: Monitor detected as down again. Location: pl-war-1 Cause: Unexpected status code: got 200, expected one of [202]

Feb 16, 2026 20:04 UTC System

Monitor is back up. Incident resolved automatically.

Feb 16, 2026 19:17 UTC System

Additional report: Monitor down detected from another location. Location: hi-hel-1 Cause: Unexpected status code: got 200, expected one of [202]

Feb 16, 2026 19:16 UTC System

Incident reopened: Monitor detected as down again. Location: uk-lon-1 Cause: Unexpected status code: got 200, expected one of [202]

Feb 16, 2026 19:11 UTC System

Monitor is back up. Incident resolved automatically.

Feb 16, 2026 19:10 UTC System

Additional report: Monitor down detected from another location. Location: de-nur-1 Cause: Unexpected status code: got 200, expected one of [202]

Feb 16, 2026 19:10 UTC System

Additional report: Monitor down detected from another location. Location: par-1 Cause: Unexpected status code: got 200, expected one of [202]

Feb 16, 2026 19:09 UTC System

Additional report: Monitor down detected from another location. Location: uk-lon-1 Cause: Unexpected status code: got 200, expected one of [202]

Feb 16, 2026 19:08 UTC System

Monitor detected as down. Location: pl-war-1 Cause: Unexpected status code: got 200, expected one of [202]