critical
RESOLVED
Keyword 2026-01-27 - Down incident at 2026-03-13 13:11
Affected Service
Keyword 2026-01-27
Started
Mar 13, 2026 13:11 UTC
Resolved
Mar 13, 2026 13:17 UTC
Duration
6 minutes
Incident Timeline
Mar 13, 2026 13:17 UTC
System
Monitor is back up. Incident resolved automatically.
Mar 13, 2026 13:15 UTC
System
Incident reopened: Monitor detected as slow response again. Location: ca-tor-1 Keyword 'miljenko' was found in response (negation mode)
Mar 13, 2026 13:14 UTC
System
Monitor is back up. Incident resolved automatically.
Mar 13, 2026 13:11 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]