critical
RESOLVED
AP - Down incident at 2026-03-30 12:03
Affected Service
AP
Started
Mar 30, 2026 12:03 UTC
Resolved
Mar 30, 2026 13:26 UTC
Duration
1.4 hours
Incident Timeline
Mar 30, 2026 13:26 UTC
System
Monitor is back up. Incident resolved automatically.
Mar 30, 2026 13:23 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 200, expected one of [202]
Mar 30, 2026 13:22 UTC
System
Incident manually resolved.
Mar 30, 2026 12:05 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 200, expected one of [202]
Mar 30, 2026 12:04 UTC
System
Incident manually resolved.
Mar 30, 2026 12:03 UTC
System
Monitor detected as down. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode) Cause: Unexpected status code: got 200, expected one of [202]