ABC

← Back to Status
critical RESOLVED

AP - Warning incident at 2026-02-06 12:55

Affected Service
AP
Started
Feb 06, 2026 12:55 UTC
Resolved
Feb 06, 2026 14:19 UTC
Duration
1.4 hours

Incident Timeline

Feb 06, 2026 14:19 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 14:18 UTC System

Incident reopened: Monitor detected as slow response again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode)

Feb 06, 2026 14:13 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 14:12 UTC System

Incident reopened: Monitor detected as down again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode) Cause: Request failed: Get "https://apptlysoft.com": net/http: timeout awaiting response headers

Feb 06, 2026 14:07 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 14:06 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 522, expected one of [200]

Feb 06, 2026 14:03 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 14:02 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 520, expected one of [200]

Feb 06, 2026 13:59 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 13:58 UTC System

Incident reopened: Monitor detected as slow response again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode)

Feb 06, 2026 13:56 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 13:55 UTC System

Incident reopened: Monitor detected as down again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode) Cause: Request failed: Get "https://apptlysoft.com": net/http: timeout awaiting response headers

Feb 06, 2026 13:54 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 13:52 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 520, expected one of [200]

Feb 06, 2026 13:44 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 13:42 UTC System

Incident reopened: Monitor detected as slow response again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode)

Feb 06, 2026 13:41 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 13:40 UTC System

Incident reopened: Monitor detected as down again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode) Cause: Request failed: Get "https://apptlysoft.com": net/http: timeout awaiting response headers

Feb 06, 2026 13:36 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 13:35 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 520, expected one of [200]

Feb 06, 2026 13:28 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 13:27 UTC System

Incident reopened: Monitor detected as slow response again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode)

Feb 06, 2026 13:24 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 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 522, expected one of [200]

Feb 06, 2026 13:20 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 13:19 UTC System

Incident reopened: Monitor detected as down again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode) Cause: Request failed: Get "https://apptlysoft.com": net/http: timeout awaiting response headers

Feb 06, 2026 13:15 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 13:12 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 522, expected one of [200]

Feb 06, 2026 13:07 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 13:06 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 522, expected one of [200]

Feb 06, 2026 13:05 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 13:03 UTC System

Incident reopened: Monitor detected as slow response again. Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode)

Feb 06, 2026 13:01 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 13:00 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 522, expected one of [200]

Feb 06, 2026 13:00 UTC System

Priority escalated to critical: Monitor is now completely down.

Feb 06, 2026 12:57 UTC System

Monitor is back up. Incident resolved automatically.

Feb 06, 2026 12:55 UTC System

Monitor detected as responding slowly. Response time: 26.1s Location: au-syd-1 Keyword 'miljenko' was found in response (negation mode)