Incident History

Back to status page
  1. Apr 23, 2026

    1. Recording 3 has recovered.

    2. Recording 3 appears to be down.

    3. Recording 2 has recovered.

    4. Recording 2 appears to be down.

    5. Recording 3 has recovered.

    6. Recording 3 appears to be down.

    7. Recording 1 has recovered.

    8. Recording 1 appears to be down.

    9. Recording 1 has recovered.

  2. Apr 22, 2026

    1. Recording 1 appears to be down.

    2. Recording 1 has recovered.

    3. Recording 1 appears to be down.

    4. Recording 3 has recovered.

    5. Recording 3 appears to be down.

    6. Recording 2 has recovered.

    7. Recording 1 has recovered.

    8. Recording 2 appears to be down.

    9. Recording 1 appears to be down.

    10. Recording 1 has recovered.

    11. Recording 1 appears to be down.

    12. Recording 1 has recovered.

    13. Recording 1 appears to be down.

    14. Recording 1 has recovered.

    15. Recording 1 appears to be down.

    16. Recording 3 has recovered.

    17. Recording 3 appears to be down.

    18. Recording 1 has recovered.

    19. Recording 1 appears to be down.

    20. Recording 1 has recovered.

    21. Recording 1 appears to be down.

    22. Recording 1 has recovered.

    23. Recording 1 appears to be down.

    24. Recording 1 has recovered.

    25. Recording 1 appears to be down.

    26. Recording 3 has recovered.

    27. Recording 3 appears to be down.

    28. Recording 3 has recovered.

    29. Recording 3 appears to be down.

  3. Apr 21, 2026

    1. Recording 2 has recovered.

    2. Recording 2 appears to be down.

    3. Session 1 has recovered.

    4. Session 1 appears to be down.

    5. Session 2 has recovered.

    6. Session 2 appears to be down.

    7. Recording 3 has recovered.

    8. Recording 2 has recovered.

    9. Recording 2 appears to be down.

    10. Recording 3 appears to be down.

    11. Recording 3 has recovered.

    12. Recording 3 appears to be down.