AP - Down incident at 2026-01-28 23:06

← Back to Status

critical RESOLVED

AP - Down incident at 2026-01-28 23:06

Affected Service

Started

Jan 28, 2026 23:06 UTC

Resolved

Jan 28, 2026 23:43 UTC

Duration

37 minutes

Incident Timeline

Jan 28, 2026 23:43 UTC System

Monitor is back up. Incident resolved automatically.

Jan 28, 2026 23:42 UTC System

Incident reopened: Monitor detected as slow response again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode)

Jan 28, 2026 23:37 UTC System

Monitor is back up. Incident resolved automatically.

Jan 28, 2026 23:35 UTC System

Incident reopened: Monitor detected as down again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode) Cause: Unexpected status code: got 522, expected one of [200]

Jan 28, 2026 23:30 UTC System

Monitor is back up. Incident resolved automatically.

Jan 28, 2026 23:29 UTC System

Incident reopened: Monitor detected as down again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode) Cause: Unexpected status code: got 522, expected one of [200]

Jan 28, 2026 23:26 UTC System

Monitor is back up. Incident resolved automatically.

Jan 28, 2026 23:24 UTC System

Incident reopened: Monitor detected as down again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode) Cause: Unexpected status code: got 522, expected one of [200]

Jan 28, 2026 23:21 UTC System

Monitor is back up. Incident resolved automatically.

Jan 28, 2026 23:17 UTC System

Incident reopened: Monitor detected as down again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode) Cause: Unexpected status code: got 522, expected one of [200]

Jan 28, 2026 23:15 UTC System

Monitor is back up. Incident resolved automatically.

Jan 28, 2026 23:14 UTC System

Incident reopened: Monitor detected as down again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode) Cause: Unexpected status code: got 522, expected one of [200]

Jan 28, 2026 23:12 UTC System

Monitor is back up. Incident resolved automatically.

Jan 28, 2026 23:09 UTC System

Incident reopened: Monitor detected as down again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode) Cause: Unexpected status code: got 522, expected one of [200]

Jan 28, 2026 23:07 UTC System

Monitor is back up. Incident resolved automatically.

Jan 28, 2026 23:06 UTC System

Monitor detected as down. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode) Cause: Unexpected status code: got 522, expected one of [200]