critical
RESOLVED
Keyword 2026-01-27 - Down incident at 2026-03-13 14:49
Affected Service
Keyword 2026-01-27
Started
Mar 13, 2026 14:49 UTC
Resolved
Mar 22, 2026 10:29 UTC
Duration
8.8 days
Incident Timeline
Mar 22, 2026 10:29 UTC
System
Monitor is back up. Incident resolved automatically.
Mar 18, 2026 11:03 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 18, 2026 11:02 UTC
System
Incident manually resolved.
Mar 13, 2026 15:01 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 14:54 UTC
System
Monitor is back up. Incident resolved automatically.
Mar 13, 2026 14: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 [202]