- Detected by Pingoru
- May 21, 2026, 03:49 PM UTC
- Resolved
- May 21, 2026, 04:02 PM UTC
- Duration
- 12m
Affected: User InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser Interface
Timeline · 2 updates
-
monitoring May 21, 2026, 03:49 PM UTC
We are aware of an issue that presented with viewing and adding comments to SIEM investigations. Our engineering has identified the issue and implemented a solution. We are actively monitoring performance.
-
resolved May 21, 2026, 04:02 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 10:22 AM UTC
- Resolved
- May 12, 2026, 10:44 AM UTC
- Duration
- 21m
Affected: Data ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData Processing
Timeline · 4 updates
-
investigating May 12, 2026, 10:22 AM UTC
We are currently investigating an issue impacting APIv4 and Bulk Export API used by Vulnerability Management. We appreciate your patience as we work to restore full functionality!
-
identified May 12, 2026, 10:29 AM UTC
We have identified the cause of the issue impacting APIv4 and Bulk Export API used by Vulnerability Management, we are also investigating a related issue impacting SIEM. We expect resolution by 11:35am UTC+1. We appreciate your patience as we work to restore full functionality!
-
monitoring May 12, 2026, 10:30 AM UTC
A fix has been implemented, our monitoring indicates recovery. We continue to monitor this incident.
-
resolved May 12, 2026, 10:44 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 02:05 AM UTC
- Resolved
- May 08, 2026, 12:49 PM UTC
- Duration
- 10h 44m
Affected: User InterfaceData Processing
Timeline · 4 updates
-
investigating May 08, 2026, 02:05 AM UTC
We are currently investigating intermittent issues in the agent management UI and delays in SIEM data processing.
-
identified May 08, 2026, 02:24 AM UTC
We have identified the issue as a vendor dependency. We are working closely with the provider to restore full service.
-
monitoring May 08, 2026, 04:51 AM UTC
Functionality has been restored, and systems are now operating normally. We are monitoring to ensure full stability.
-
resolved May 08, 2026, 12:49 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 02:48 PM UTC
- Resolved
- May 05, 2026, 04:43 PM UTC
- Duration
- 1h 55m
Affected: Data ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData Processing
Timeline · 4 updates
-
identified May 05, 2026, 02:48 PM UTC
We have identified an issue that caused delays in the creation of Investigations for SIEM (InsightIDR) and Managed Detection and Response customers. A fix has been deployed. Investigations that should have been created between 11:25 and 13:50 UTC on May 5, 2026 may still be delayed. We are actively replaying impacted alerts and working to ensure all missing Investigations are generated as quickly as possible.
-
identified May 05, 2026, 03:08 PM UTC
Update: For Managed Detection and Response (MDR) customers, Rapid7 Managed alerts were not impacted. However, Custom and Contextual alerts (not triaged by the Rapid7 SOC) may have experienced delays in Investigation creation during this time window.
-
identified May 05, 2026, 03:58 PM UTC
Update: Replay of impacted alerts for the CA and AP regions has been completed.
-
resolved May 05, 2026, 04:43 PM UTC
Update: Replay of impacted alerts for all regions has been completed.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 11:21 AM UTC
- Resolved
- Apr 27, 2026, 02:51 PM UTC
- Duration
- 3d 3h
Affected: Data ProcessingData Processing
Timeline · 4 updates
-
investigating Apr 24, 2026, 11:21 AM UTC
We are currently investigating a slowdown in processing Alerts and creating investigations in ap-southeast-2 and eu-central-1 regions.
-
investigating Apr 24, 2026, 12:37 PM UTC
Impacted services have been scaled to process the backlog of investigations and are now fully caught up. We will continue to closely monitor service health to ensure ongoing stability.
-
monitoring Apr 24, 2026, 12:38 PM UTC
Impacted services have been scaled to process the backlog of investigations and are now fully caught up. We will continue to closely monitor service health to ensure ongoing stability.
-
resolved Apr 27, 2026, 02:51 PM UTC
We have confirmed that all processing is up to date and operating as normal.
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 05:17 PM UTC
- Resolved
- Apr 17, 2026, 07:05 PM UTC
- Duration
- 1h 48m
Affected: User InterfaceData Processing
Timeline · 3 updates
-
investigating Apr 17, 2026, 05:17 PM UTC
We are currently investigating an issue where InsightAppSec scans are failing to initiate or complete successfully.
-
monitoring Apr 17, 2026, 06:09 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 17, 2026, 07:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 04:19 PM UTC
- Resolved
- Apr 15, 2026, 06:34 PM UTC
- Duration
- 2h 15m
Affected: Data ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData ProcessingData Processing
Timeline · 3 updates
-
identified Apr 15, 2026, 04:19 PM UTC
We have identified an issue impacting Attack Surface Management (Surface Command). Customers may experience failure of the Command Platform import feed. Our engineering teams have identified the root cause, applied the remediation and are actively restarting the impacted import feed due by 17:30 UTC - the time to completion of the import feed will vary based upon your environment size. Updates will be posted here as they become available.
-
monitoring Apr 15, 2026, 05:18 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 15, 2026, 06:34 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 13, 2026, 03:55 PM UTC
- Resolved
- Apr 15, 2026, 05:43 PM UTC
- Duration
- 2d 1h
Affected: User InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser Interface
Timeline · 6 updates
-
investigating Apr 13, 2026, 03:55 PM UTC
We are investigating an issue affecting the Automation Reporting Homepage at the primary landing page. Specific metrics, including "Time Saved" and "Time to Human Decision," are currently failing to load on this dashboard. Historical data remains secure on the backend, but we are currently verifying if new data is being successfully recorded. While these visual indicators are not appearing in the UI, users can still access reporting metrics through other areas of the product.
-
identified Apr 13, 2026, 04:33 PM UTC
The root cause has been identified and our teams are actively working on a remediation. While these visual indicators are currently absent from the UI, historical data remains secure on the backend. We have confirmed that no data is being lost during this period; once the fix is deployed, all missing data will be backfilled and restored to the dashboard.
-
identified Apr 13, 2026, 04:35 PM UTC
We are continuing to work on a fix for this issue.
-
identified Apr 14, 2026, 03:57 PM UTC
We are continuing to work on the fix for this issue. Our engineering teams have established a clear path to recovery, and we can confirm that all missing data will be backfilled automatically. No action is required from customers at this time, as metrics will be restored to the dashboard as soon as the remediation is deployed.
-
monitoring Apr 15, 2026, 04:09 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 15, 2026, 05:43 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 13, 2026, 03:45 PM UTC
- Resolved
- Apr 13, 2026, 04:35 PM UTC
- Duration
- 50m
Affected: User InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser Interface
Timeline · 3 updates
-
investigating Apr 13, 2026, 03:45 PM UTC
We are currently investigating an issue affecting Command Platform Login and Navigation between Command Platform Experiences. Customers may experience login latency and latency navigating through the User Interface. Our engineering teams are actively working to identify the cause and restore normal service. Updates will be posted here as they become available.
-
monitoring Apr 13, 2026, 04:14 PM UTC
A fix has been implemented and we are continuing to monitor our recovery.
-
resolved Apr 13, 2026, 04:35 PM UTC
This incident has been resolved. Thank you for your patience and cooperation as we investigated and remediated.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 05:12 AM UTC
- Resolved
- Apr 09, 2026, 09:28 PM UTC
- Duration
- 16h 15m
Affected: Data ProcessingData Processing
Timeline · 3 updates
-
investigating Apr 09, 2026, 05:12 AM UTC
Some customers in US East and US West are experiencing a higher than normal volume of investigations. The issue is no longer occurring, however we are looking into alerts received within the timeframe - 6pm to 12:30am UTC. If you believe you have been affected by this issue, please log a support case with the subject line: increased-investigation-volume.
-
monitoring Apr 09, 2026, 08:55 AM UTC
Between 6:00 PM and 12:30 AM UTC, customers in the US East and US West regions experienced a higher than normal volume of investigations. This issue has been resolved and systems are performing normally. For our managed customers, the SOC is currently processing the remaining backlog of investigations
-
resolved Apr 09, 2026, 09:28 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2026, 05:59 PM UTC
- Resolved
- Mar 13, 2026, 07:59 PM UTC
- Duration
- 1h 59m
Affected: User InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceData ProcessingData ProcessingNexpose Console Updates and License Activation
Timeline · 3 updates
-
investigating Mar 13, 2026, 05:59 PM UTC
We are currently investigating an issue impacting log-in to the Command Platform.
-
monitoring Mar 13, 2026, 06:31 PM UTC
We have recovered, and login is now accessible across all regions we continue to monitor the situation.
-
resolved Mar 13, 2026, 07:59 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2026, 03:09 PM UTC
- Resolved
- Mar 18, 2026, 08:24 PM UTC
- Duration
- 7d 5h
Affected: User InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser Interface
Timeline · 3 updates
-
identified Mar 11, 2026, 03:09 PM UTC
We are aware of an unexpected increase in the number of new investigations being created, starting at 11:00 AM UTC. This was caused by a configuration error that briefly re-enabled a set of legacy detections. We have since disabled these detections and are working to identify and mitigate the impact on user dashboards.This issue impacts SIEM and Services customers. Impact: Users may see a spike in noisy investigations created during this 2-hour window.
-
monitoring Mar 11, 2026, 03:36 PM UTC
We are aware of an unexpected increase in the number of new investigations being created, starting at 11:00 AM UTC. This was caused by a configuration error that briefly re-enabled a set of legacy detections. We have since disabled these detections and are working to identify and mitigate the impact on user dashboards.This issue impacts SIEM and Services customers. Impact: Users may see a spike in noisy investigations created during this 2-hour window. **Next Steps: We are currently evaluating a bulk cleanup for the noisy investigations.
-
resolved Mar 18, 2026, 08:24 PM UTC
We have contacted all affected customers via email or their account teams and shared remediation plans for investigations created during the affected window. Our engineering teams have also begun the cleanup process. Please note: We are transitioning to direct updates for impacted customers, and this status page will no longer be updated. If you believe you were affected but have not received communication, please contact Rapid7 Support or reach out to your account team.
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2026, 02:48 PM UTC
- Resolved
- Mar 18, 2026, 08:43 AM UTC
- Duration
- 6d 17h
Affected: Data ProcessingData Processing
Timeline · 8 updates
-
investigating Mar 11, 2026, 02:48 PM UTC
We are currently investigating an issue with an upgrade to collectors in the EU and US East 1 regions
-
identified Mar 11, 2026, 04:56 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Mar 11, 2026, 10:28 PM UTC
The issue has been identified by our Engineering team and a fix is being tested.
-
identified Mar 12, 2026, 02:20 AM UTC
We are continuing to work on a fix for this issue.
-
identified Mar 12, 2026, 02:23 AM UTC
We are continuing to work on a fix for this issue.
-
monitoring Mar 12, 2026, 02:26 AM UTC
A fix has now been implemented and we are monitoring the results.
-
monitoring Mar 16, 2026, 10:55 AM UTC
We continue to monitor the results of the fix implemented.
-
resolved Mar 18, 2026, 08:43 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 09, 2026, 06:26 PM UTC
- Resolved
- Mar 09, 2026, 11:08 PM UTC
- Duration
- 4h 41m
Affected: User InterfaceUser InterfaceUser InterfaceUser InterfaceData ProcessingData ProcessingData ProcessingData Processing
Timeline · 5 updates
-
investigating Mar 09, 2026, 06:26 PM UTC
We are currently investigating an issue impacting InsightVM Dashboards across multiple regions. Our teams are currently investigating this issue and will provide further updates as we make progress.
-
investigating Mar 09, 2026, 07:27 PM UTC
We are continuing to investigate this issue.
-
identified Mar 09, 2026, 07:46 PM UTC
Rapid7 has identified the issue impacting Dashboards loading and is actively working on mitigation.
-
monitoring Mar 09, 2026, 08:07 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 09, 2026, 11:08 PM UTC
This incident has now been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 12:53 AM UTC
- Resolved
- Mar 03, 2026, 02:07 AM UTC
- Duration
- 1h 14m
Affected: User InterfaceData Processing
Timeline · 3 updates
-
investigating Mar 03, 2026, 12:53 AM UTC
We are currently investigating an issue within Vulnerability Management specifically affecting our US2 customers. During this time, you may experience login failures in Exposure Analytics or receive errors when calling the Public v4 API. Our engineering teams are actively working to identify the cause and restore normal service. Impacted Region: US2 First Noticed: March 3, 2026 @ 00:12 UTC Updates will be posted here as they become available.
-
monitoring Mar 03, 2026, 01:07 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 03, 2026, 02:07 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 01, 2026, 02:05 PM UTC
- Resolved
- Mar 18, 2026, 02:32 PM UTC
- Duration
- 17d
Affected: User InterfaceUser InterfaceData ProcessingData Processing
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- Feb 05, 2026, 09:11 AM UTC
- Resolved
- Feb 05, 2026, 09:33 AM UTC
- Duration
- 22m
Affected: User InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser Interface
Timeline · 3 updates
-
investigating Feb 05, 2026, 09:11 AM UTC
We are currently investigating an issue in which the command platform is inaccessible
-
monitoring Feb 05, 2026, 09:19 AM UTC
We have recovered across all regions, we continue to monitor.
-
resolved Feb 05, 2026, 09:33 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 30, 2025, 09:06 PM UTC
- Resolved
- Nov 30, 2025, 10:14 PM UTC
- Duration
- 1h 7m
Affected: User Interface
Timeline · 2 updates
-
identified Nov 30, 2025, 09:06 PM UTC
We are currently investigating an issue impacting InsightVM Dashboards and v4 API. Our teams have identified the root cause, and recovery efforts are actively in progress. We will provide further updates as we make progress.
-
resolved Nov 30, 2025, 10:14 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 01:34 PM UTC
- Resolved
- Nov 19, 2025, 12:59 AM UTC
- Duration
- 11h 24m
Affected: User Interface
Timeline · 7 updates
-
investigating Nov 17, 2025, 04:00 PM UTC
We are aware of a performance degradation affecting Vulnerability Management Dashboards, Remediation Projects, and Goals. Some requests for a subset of dashboard cards may be slower than usual or fail to load. Our teams are actively investigating and working to restore normal performance.
-
investigating Nov 17, 2025, 10:56 PM UTC
Our team continues to investigate the performance degradation affecting Vulnerability Management Dashboards, Remediation Projects, and Goals in the US1 region. Some requests may still be slower than usual or fail to load. We will provide another update as soon as more information becomes available.
-
investigating Nov 18, 2025, 02:07 AM UTC
We are continuing our investigation into the performance degradation affecting Vulnerability Management Dashboards, Remediation Projects, and Goals in the US1 region. Some requests may still be slower than usual or fail to load. Further updates will be provided as soon as more information becomes available.
-
monitoring Nov 18, 2025, 01:34 PM UTC
Through our investigation, performance and availability has improved. We continue to monitor performance across Vulnerability Management Dashboards, Remediation Projects, and Goals in the US1 region.
-
investigating Nov 18, 2025, 03:30 PM UTC
We are aware of a continued performance degradation affecting Vulnerability Management Dashboards, Remediation Projects, and Goals. Some requests for a subset of dashboard cards may be slower than usual or fail to load. Our teams are actively investigating and working to restore normal performance.
-
monitoring Nov 19, 2025, 04:01 AM UTC
Performance for Vulnerability Management Dashboards, Remediation Projects, and Goals in the US1 region has stabilized. Our engineering teams continue to investigate the earlier performance degradation to ensure it does not recur.
-
resolved Nov 20, 2025, 12:59 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 01:10 PM UTC
- Resolved
- Nov 18, 2025, 05:24 PM UTC
- Duration
- 4h 14m
Affected: User InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser InterfaceUser Interface
Timeline · 3 updates
-
investigating Nov 18, 2025, 01:10 PM UTC
We are currently investigating an issue affecting Threat Command. Customers may experience intermittent login failure, API and user interface errors. Our engineering teams are actively working to identify the cause and restore normal service.
-
monitoring Nov 18, 2025, 03:38 PM UTC
We are continuing to monitor the recovery from this incident and are seeing steady improvements in service availability.
-
resolved Nov 18, 2025, 05:24 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 04, 2025, 01:52 PM UTC
- Resolved
- Nov 04, 2025, 06:17 PM UTC
- Duration
- 4h 25m
Affected: User InterfaceUser InterfaceUser InterfaceUser Interface
Timeline · 5 updates
-
investigating Nov 04, 2025, 01:52 PM UTC
We are currently investigating an issue affecting InsightIDR. Users may experience degraded performance impacting data collection, processing, and elements of the user interface.
-
identified Nov 04, 2025, 02:22 PM UTC
The issue has been identified and a resolution is being implemented.
-
identified Nov 04, 2025, 02:34 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Nov 04, 2025, 02:54 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 04, 2025, 06:17 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 29, 2025, 05:05 PM UTC
- Resolved
- Oct 29, 2025, 09:51 PM UTC
- Duration
- 4h 46m
Timeline · 5 updates
-
identified Oct 29, 2025, 05:05 PM UTC
Rapid7 is currently aware of a degradation issue with one of our service providers. As a result, some cloud based event sources and collectors may be effected. Our teams are closely monitoring the situation. We appreciate your patience and will provide updates as more information becomes available.
-
identified Oct 29, 2025, 05:38 PM UTC
We are continuing to work on a fix for this issue.
-
identified Oct 29, 2025, 05:41 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Oct 29, 2025, 07:28 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 29, 2025, 09:51 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 28, 2025, 01:41 AM UTC
- Resolved
- Oct 28, 2025, 10:00 AM UTC
- Duration
- 8h 18m
Timeline · 3 updates
-
identified Oct 28, 2025, 01:41 AM UTC
We’ve identified an issue causing delays in log search data for some customers. Alert delivery remains unaffected. Our engineering team is actively investigating the issue.
-
monitoring Oct 28, 2025, 01:53 AM UTC
Engineering teams have identified the cause and have taken measures to remediate.
-
resolved Oct 28, 2025, 10:00 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 07:30 PM UTC
- Resolved
- Oct 21, 2025, 12:11 PM UTC
- Duration
- 16h 40m
Affected: User InterfaceData Processing
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Oct 16, 2025, 10:07 PM UTC
- Resolved
- Oct 17, 2025, 12:12 AM UTC
- Duration
- 2h 5m
Affected: User Interface
Timeline · 3 updates
-
investigating Oct 16, 2025, 10:07 PM UTC
We are currently investigating an issue where the cloud reporting page is failing to load or is unavailable for some users. During this time, users may be unable to generate new cloud reports. Our engineers are diagnosing the issue to determine the root cause and restore functionality.
-
monitoring Oct 16, 2025, 10:18 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 17, 2025, 12:12 AM UTC
This incident has been resolved.
Read the full incident report →