ABC

← Back to Status
critical RESOLVED

JP Standard - Warning incident at 2026-03-06 10:26

Affected Service
JP Standard
Started
Mar 06, 2026 10:26 UTC
Resolved
Mar 06, 2026 10:35 UTC
Duration
9 minutes

Incident Timeline

Mar 06, 2026 10:35 UTC System

Monitor is back up. Incident resolved automatically.

Mar 06, 2026 10:34 UTC System

Incident reopened: Monitor detected as down again. Location: par-1 Cause: Unexpected status code: got 502, expected one of [200]

Mar 06, 2026 10:32 UTC System

Monitor is back up. Incident resolved automatically.

Mar 06, 2026 10:31 UTC System

Incident reopened: Monitor detected as slow response again. Location: par-1

Mar 06, 2026 10:30 UTC System

Monitor is back up. Incident resolved automatically.

Mar 06, 2026 10:29 UTC System

Incident reopened: Monitor detected as down again. Location: par-1 Cause: Unexpected status code: got 502, expected one of [200]

Mar 06, 2026 10:29 UTC System

Priority escalated to critical: Monitor is now completely down.

Mar 06, 2026 10:28 UTC System

Monitor is back up. Incident resolved automatically.

Mar 06, 2026 10:26 UTC System

Additional report: Monitor slow response detected from another location. Response time: 19.1s Location: de-nur-1

Mar 06, 2026 10:26 UTC System

Additional report: Monitor slow response detected from another location. Response time: 17.9s Location: hi-hel-1

Mar 06, 2026 10:26 UTC System

Additional report: Monitor slow response detected from another location. Response time: 19.1s Location: uk-lon-1

Mar 06, 2026 10:26 UTC System

Monitor detected as responding slowly. Response time: 17.9s Location: par-1