Nobl9 Outage History

Nobl9 is up right now

Pingoru has recorded 50 incidents for Nobl9: 4 in the last 12 months and 0 in the last 90 days.

Source: status.nobl9.com

50incidents recorded
4last 12 months
0last 90 days
32 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Nobl9 in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 524 (0%)

Incidents, newest first

Minor March 24, 2026 Partial service degradation affecting SLO processing –

Started Mar 24, 2026, 09:00 AM UTC· resolved Mar 24, 2026, 09:00 AM UTC

  1. resolved Mar 24, 2026, 09:51 AM UTC

    We are experiencing partial service degradation affecting SLO processing. Alerting, reports, and SLO functionality may be impacted for a subset of users. The degradation was mitigated and resolved within 20min.

Read the full incident report →

Notice February 25, 2026 Downgraded replay and charts performance –

Started Feb 25, 2026, 05:00 AM UTC· resolved Feb 25, 2026, 05:00 AM UTC

  1. resolved Feb 25, 2026, 06:08 AM UTC

    We experienced a temporary infrastructure issue affecting one of our Kubernetes worker nodes. This resulted in degraded Replay performance and intermittent chart issues.

Read the full incident report →

Minor October 3, 2025 Silenced Alerts Might Still Fire 4h 51m Alerting

Started Oct 03, 2025, 06:15 PM UTC· resolved Oct 03, 2025, 11:06 PM UTC

  1. investigating Oct 03, 2025, 06:15 PM UTC

    We are currently investigating an incident where silenced alerts may still fire.

  2. investigating Oct 03, 2025, 07:26 PM UTC

    We are continuing to look into this issue.

  3. identified Oct 03, 2025, 09:23 PM UTC

    We have identified the issue. Most SLOs and alert policies are not impacted and we are working on deploying a fix.

  4. monitoring Oct 03, 2025, 10:53 PM UTC

    A fix was deployed to production.

  5. resolved Oct 03, 2025, 11:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 6, 2025 Chart Data Viewing, Data processing and Alerts are delayed on US1 1h 5m Data Intake - Agent stable and beta, Data Intake - Direct stable, Data Intake - Direct beta, Chart Data and 1 more

Started Aug 06, 2025, 03:55 AM UTC· resolved Aug 06, 2025, 05:00 AM UTC

  1. investigating Aug 06, 2025, 03:55 AM UTC

    Nobl9 is experiencing delays in sending alerts and data on the charts. Our engineering team is actively investigating the problem. If you have any questions please reach out to [email protected]

  2. identified Aug 06, 2025, 04:03 AM UTC

    Charts are back, processing and alerting are recovering.

  3. monitoring Aug 06, 2025, 04:06 AM UTC

    Charts are back, processing and alerting are recovering.

  4. monitoring Aug 06, 2025, 04:16 AM UTC

    Charts, processing, and alerting systems are fully operational. However, if any alerts were generated during the incident, they may be delayed. If you have any questions, please feel free to reach out to support at [email protected].

  5. resolved Aug 06, 2025, 05:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 17, 2025 Chart data delayed 2h

Started Jul 17, 2025, 09:00 AM UTC· resolved Jul 17, 2025, 11:00 AM UTC

  1. resolved Jul 17, 2025, 03:15 PM UTC

    Between 11:00 UTC and 14:10 UTC, data in all charts, dashboards, and reports may have been delayed. The delay began to grow around 11:00 UTC and was resolved by 14:10 UTC. All affected components have now caught up, and data is current.

Read the full incident report →

Minor June 9, 2025 Downgraded processing and replay performance 12m Data Intake - Direct beta, Chart Data, Replay, SLI Analyzer

Started Jun 09, 2025, 03:53 PM UTC· resolved Jun 09, 2025, 04:05 PM UTC

  1. identified Jun 09, 2025, 03:53 PM UTC

    We have identified an issue causing degraded performance of replay and delays in processing and data intake. Some replays will take longer to finish, some may need to be retried.

  2. monitoring Jun 09, 2025, 04:01 PM UTC

    The issue has been resolved, we are monitoring the situation.

  3. resolved Jun 09, 2025, 04:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 5, 2025 Downgraded Replay and SLI Analyzer performance 21m Replay, SLI Analyzer

Started Jun 05, 2025, 09:00 AM UTC· resolved Jun 05, 2025, 09:22 AM UTC

  1. investigating Jun 05, 2025, 09:16 AM UTC

    Some replays may take longer to finish. Some replays will need to be re-run.

  2. resolved Jun 05, 2025, 09:22 AM UTC

    Issue has been resolved

Read the full incident report →

Major March 31, 2025 Reliability Rollup Report based on rolling time windows cannot be displayed or created 9h 23m Reports, Reports

Started Mar 31, 2025, 03:25 PM UTC· resolved Apr 01, 2025, 12:48 AM UTC

  1. investigating Mar 31, 2025, 03:25 PM UTC

    The bug affects the creation and display of RRR (Reliability Rollup Report) reports that use the “rolling” window “Last Month” and are created/viewed on March 31st and possibly March 30th. We are investigating the issue and possible solutions.

  2. identified Mar 31, 2025, 04:09 PM UTC

    The issue has been identified and it will be automatically resolved once the 1st of April begins (UTC time zone), which will happen in around 6 hours. The issue is only affecting dates which do not have corresponding days in the previous month, i.e. 29th, 30th and 31st of March. The 28th of March is not affected as it has a corresponding date in the previous month, February 28th. Work on a permanent fix to the affected code is in progress.

  3. resolved Apr 01, 2025, 12:48 AM UTC

    The issue is resolved since 1st of April in (UTC time zone). Work on a permanent fix to the affected code is in progress, but the underlying issue no longer affects creating or viewing reports.

Read the full incident report →

Critical February 17, 2025 Outage on Us1 52m Data Intake - Agent stable and beta, Data Intake - Direct stable, Data Intake - Direct beta, Chart Data and 1 more

Started Feb 17, 2025, 01:52 AM UTC· resolved Feb 17, 2025, 02:45 AM UTC

  1. investigating Feb 17, 2025, 01:52 AM UTC

    We are currently investigating an issue impacting US1 processing and the web application.

  2. investigating Feb 17, 2025, 01:54 AM UTC

    We are continuing to investigate this issue.

  3. identified Feb 17, 2025, 01:56 AM UTC

    We've identified the cause and are working on a fix

  4. identified Feb 17, 2025, 02:11 AM UTC

    We are continuing to work on a fix for this issue.

  5. monitoring Feb 17, 2025, 02:17 AM UTC

    The fix has been implemented and services are now available. Data may take some time to recover.

  6. monitoring Feb 17, 2025, 02:38 AM UTC

    Live data and alerts are fully functional, but historical chart data from during the incident is not yet available

  7. resolved Feb 17, 2025, 02:45 AM UTC

    The system is now fully operational.

Read the full incident report →

Minor December 17, 2024 Post-Release API Availability –

Started Dec 17, 2024, 08:00 AM UTC· resolved Dec 17, 2024, 08:00 AM UTC

  1. resolved Dec 17, 2024, 02:59 PM UTC

    Users of app.nobl9.com may have encountered errors in the UI while loading SLOs caused by post-release API unavailability. Our engineering team is actively working to improve API reliability during releases to minimize user impact. Additionally, we are reviewing and enhancing our error-handling processes to prevent similar issues in the future.

Read the full incident report →

Major December 16, 2024 General API and Web unavailability 1h 5m Chart Data, Web App, API Requests, Data Export and 2 more

Started Dec 16, 2024, 05:41 PM UTC· resolved Dec 16, 2024, 06:47 PM UTC

  1. identified Dec 16, 2024, 05:41 PM UTC

    Nobl9 is currently experiencing API related issues. Processing and Alerting is not affected.

  2. identified Dec 16, 2024, 05:42 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Dec 16, 2024, 05:49 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Dec 16, 2024, 06:47 PM UTC

    This incident has been resolved.

Read the full incident report →