Bigeye incident

Degraded performance on Slack notifications.

Major Resolved View vendor source →

Bigeye experienced a major incident on October 28, 2022 affecting API and UI, lasting 9h 39m. The incident has been resolved; the full update timeline is below.

Started
Oct 28, 2022, 03:56 PM UTC
Resolved
Oct 29, 2022, 01:35 AM UTC
Duration
9h 39m
Detected by Pingoru
Oct 28, 2022, 03:56 PM UTC

Affected components

APIUI

Update timeline

  1. investigating Oct 28, 2022, 03:56 PM UTC

    We are currently investigating an issue with Slack notifications.

  2. investigating Oct 28, 2022, 04:26 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 28, 2022, 04:57 PM UTC

    We are continuing to investigate this issue.

  4. investigating Oct 28, 2022, 05:26 PM UTC

    We are continuing to investigate this issue.

  5. investigating Oct 28, 2022, 05:56 PM UTC

    We are continuing to investigate this issue.

  6. investigating Oct 28, 2022, 06:26 PM UTC

    A root cause has been found, and we are working on fixing the issue.

  7. investigating Oct 28, 2022, 06:56 PM UTC

    We are continuing to investigate this issue.

  8. investigating Oct 28, 2022, 07:27 PM UTC

    We are continuing to investigate this issue.

  9. investigating Oct 28, 2022, 07:55 PM UTC

    We are continuing to investigate this issue.

  10. investigating Oct 28, 2022, 08:26 PM UTC

    We are continuing to investigate this issue.

  11. investigating Oct 28, 2022, 08:57 PM UTC

    We are continuing to investigate this issue.

  12. investigating Oct 28, 2022, 09:35 PM UTC

    We are continuing to investigate this issue.

  13. investigating Oct 28, 2022, 10:06 PM UTC

    We are continuing to investigate this issue.

  14. investigating Oct 28, 2022, 10:38 PM UTC

    We are continuing to investigate this issue.

  15. investigating Oct 28, 2022, 11:32 PM UTC

    We are continuing to investigate this issue.

  16. investigating Oct 29, 2022, 12:14 AM UTC

    We are continuing to investigate this issue.

  17. investigating Oct 29, 2022, 12:41 AM UTC

    We are continuing to investigate this issue.

  18. investigating Oct 29, 2022, 01:17 AM UTC

    We are continuing to investigate this issue.

  19. resolved Oct 29, 2022, 01:35 AM UTC

    This incident has been resolved.