ABC

← Back to Status
critical RESOLVED

Keyword 2026-01-27 - Down incident at 2026-01-28 23:08

Affected Service
Keyword 2026-01-27
Started
Jan 28, 2026 23:08 UTC
Resolved
Jan 28, 2026 23:43 UTC
Duration
35 minutes

Incident Timeline

Jan 28, 2026 23:43 UTC System

Monitor is back up. Incident resolved automatically.

Jan 28, 2026 23:40 UTC System

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

Jan 28, 2026 23:39 UTC System

Monitor is back up. Incident resolved automatically.

Jan 28, 2026 23:38 UTC System

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

Jan 28, 2026 23:35 UTC System

Monitor is back up. Incident resolved automatically.

Jan 28, 2026 23:29 UTC System

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

Jan 28, 2026 23:25 UTC System

Monitor is back up. Incident resolved automatically.

Jan 28, 2026 23:24 UTC System

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

Jan 28, 2026 23:22 UTC System

Monitor is back up. Incident resolved automatically.

Jan 28, 2026 23:20 UTC System

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

Jan 28, 2026 23:19 UTC System

Monitor is back up. Incident resolved automatically.

Jan 28, 2026 23:17 UTC System

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

Jan 28, 2026 23:13 UTC System

Monitor is back up. Incident resolved automatically.

Jan 28, 2026 23:08 UTC System

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