Keyword 2026-01-27 - Down incident at 2026-03-13 10:49

← Back to Status

critical RESOLVED

Keyword 2026-01-27 - Down incident at 2026-03-13 10:49

Affected Service

Keyword 2026-01-27

Started

Mar 13, 2026 10:49 UTC

Resolved

Mar 13, 2026 11:32 UTC

Duration

43 minutes

Incident Timeline

Mar 13, 2026 11:32 UTC System

Monitor is back up. Incident resolved automatically.

Mar 13, 2026 11:23 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 200, expected one of [202]

Mar 13, 2026 11:18 UTC System

Monitor is back up. Incident resolved automatically.

Mar 13, 2026 11:15 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 200, expected one of [202]

Mar 13, 2026 11:12 UTC System

Monitor is back up. Incident resolved automatically.

Mar 13, 2026 10:58 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 200, expected one of [302]

Mar 13, 2026 10:55 UTC System

Monitor is back up. Incident resolved automatically.

Mar 13, 2026 10:49 UTC System

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