ARMO incident

api is down

Major Resolved View vendor source →

ARMO experienced a major incident on March 4, 2026 affecting api, lasting 4h 8m. The incident has been resolved; the full update timeline is below.

Started
Mar 04, 2026, 01:34 PM UTC
Resolved
Mar 04, 2026, 05:42 PM UTC
Duration
4h 8m
Detected by Pingoru
Mar 04, 2026, 01:34 PM UTC

Affected components

api

Update timeline

  1. investigating Mar 04, 2026, 01:34 PM UTC

    api went down.

  2. resolved Mar 04, 2026, 01:39 PM UTC

    api recovered.

  3. investigating Mar 04, 2026, 01:44 PM UTC

    api went down.

  4. resolved Mar 04, 2026, 01:51 PM UTC

    api recovered.

  5. investigating Mar 04, 2026, 03:37 PM UTC

    api went down.

  6. resolved Mar 04, 2026, 03:41 PM UTC

    api recovered.

  7. investigating Mar 04, 2026, 04:55 PM UTC

    api went down.

  8. resolved Mar 04, 2026, 04:58 PM UTC

    api recovered.

  9. investigating Mar 04, 2026, 04:58 PM UTC

    api went down.

  10. resolved Mar 04, 2026, 05:06 PM UTC

    api recovered.

  11. investigating Mar 04, 2026, 05:07 PM UTC

    api went down.

  12. resolved Mar 04, 2026, 05:13 PM UTC

    api recovered.

  13. investigating Mar 04, 2026, 05:14 PM UTC

    api went down.

  14. resolved Mar 04, 2026, 05:20 PM UTC

    api recovered.

  15. investigating Mar 04, 2026, 05:27 PM UTC

    api went down.

  16. resolved Mar 04, 2026, 05:34 PM UTC

    api recovered.

  17. investigating Mar 04, 2026, 05:36 PM UTC

    api went down.

  18. resolved Mar 04, 2026, 05:42 PM UTC

    api recovered.