Nobl9 incident

Charts data and Alerts are delayed

Notice Resolved View vendor source →

Nobl9 experienced a notice incident on August 28, 2022 affecting Chart Data and Data Export and 1 more component, lasting 15h 4m. The incident has been resolved; the full update timeline is below.

Started
Aug 28, 2022, 07:14 AM UTC
Resolved
Aug 28, 2022, 10:19 PM UTC
Duration
15h 4m
Detected by Pingoru
Aug 28, 2022, 07:14 AM UTC

Affected components

Chart DataData ExportAlerting

Update timeline

  1. investigating Aug 28, 2022, 07:14 AM UTC

    We are currently investigating an issue with our error budget calculation service. Charts data and Alerts are delayed.

  2. identified Aug 28, 2022, 07:42 AM UTC

    We are working on recovery. Live data on charts and alerts are still delayed

  3. monitoring Aug 28, 2022, 08:23 AM UTC

    All Alerts are working correctly, the charts will be fully functional any time soon. We are monitoring the situation.

  4. monitoring Aug 28, 2022, 09:00 AM UTC

    We are still working on making the charts fully functional and monitoring the situation.

  5. monitoring Aug 28, 2022, 09:31 AM UTC

    We are checking if any data was lost during the incident and monitoring the situation.

  6. monitoring Aug 28, 2022, 10:05 AM UTC

    No changes since the last update. We are still monitoring the situation.

  7. monitoring Aug 28, 2022, 10:42 AM UTC

    We are continuing to monitor the situation.

  8. monitoring Aug 28, 2022, 11:14 AM UTC

    Chart Data and Alerts have recovered and are operating normally. We are monitoring the situation.

  9. monitoring Aug 28, 2022, 11:54 AM UTC

    No changes since the last update. We are still monitoring the situation.

  10. monitoring Aug 28, 2022, 01:01 PM UTC

    We are continuing to monitor the situation.

  11. monitoring Aug 28, 2022, 03:24 PM UTC

    All Chart Data and Alerts are operational, but we might have some gaps in data export at the time when the incident happened (between 7-8 UTC). We continue to monitor this issue.

  12. resolved Aug 28, 2022, 10:19 PM UTC

    This incident has been resolved.