- Detected by Pingoru
- Oct 14, 2026, 06:50 AM UTC
- Resolved
- Oct 16, 2026, 11:55 AM UTC
- Duration
- 2d 5h
Affected: us-5aus08
Timeline · 5 updates
-
investigating Oct 14, 2026, 06:50 AM UTC
We are aware of and actively investigating data latency in Exposure Management that are impacting certain users. We will provide periodic updates as our engineers continue working on this issue. The issue is related to an ongoing incident with our service provider.
-
identified Oct 14, 2026, 12:00 PM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
-
identified Oct 14, 2026, 09:16 PM UTC
We have implemented a fix for the issue and are monitoring the recovery.
-
monitoring Oct 14, 2026, 09:17 PM UTC
We have implemented a fix for the issue and are monitoring the recovery.
-
resolved Oct 16, 2026, 11:55 AM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Oct 14, 2026, 12:30 AM UTC
- Resolved
- Oct 14, 2026, 12:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 14, 2026, 11:56 AM UTC
Between 00:37 UTC to 00:56 UTC, the Cyber Exposure Feed was temporarily unresponsive and the issue has been resolved.. The issue has been resolved. We apologize for any inconvenience this may have caused.
Read the full incident report →
- Detected by Pingoru
- Oct 12, 2026, 05:11 PM UTC
- Resolved
- Oct 14, 2026, 06:02 PM UTC
- Duration
- 2d
Timeline · 3 updates
-
investigating Oct 12, 2026, 05:11 PM UTC
We are aware of and actively investigating issues with TPM GUI slowness and 502/503 errors certain users. We will provide periodic updates as our engineers continue working on this issue.
-
monitoring Oct 12, 2026, 10:54 PM UTC
We have implemented a fix for the issue and are monitoring the recovery.
-
resolved Oct 14, 2026, 06:02 PM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Oct 12, 2026, 06:47 AM UTC
- Resolved
- Oct 12, 2026, 10:25 AM UTC
- Duration
- 3h 38m
Affected: GOV01
Timeline · 4 updates
-
investigating Oct 12, 2026, 06:47 AM UTC
We are aware of and actively investigating scan processing and explore findings and asset pages delays that are impacting certain users. We will provide periodic updates as our engineers continue working on this issue.
-
identified Oct 12, 2026, 07:47 AM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
-
monitoring Oct 12, 2026, 09:03 AM UTC
We have implemented a fix for the issue and are monitoring the recovery.
-
resolved Oct 12, 2026, 10:25 AM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Oct 08, 2026, 07:10 PM UTC
- Resolved
- Oct 09, 2026, 08:26 AM UTC
- Duration
- 13h 15m
Affected: AP-SYD-1BR01CA01FRAIN01JP01SINGUK-LON-1US-1AUS-2AUS-3AUS-4AUS-5AUS07US08GOV01ca02
Timeline · 4 updates
-
investigating Oct 08, 2026, 07:10 PM UTC
We are aware of and actively investigating issues with scheduled scans failing to launch for certain users. We will provide periodic updates as our engineers continue working on this issue.
-
investigating Oct 08, 2026, 07:11 PM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
-
identified Oct 08, 2026, 07:52 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Oct 09, 2026, 08:26 AM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Oct 06, 2026, 10:19 PM UTC
- Resolved
- Oct 13, 2026, 07:49 AM UTC
- Duration
- 6d 9h
Affected: AP-SYD-1BR01CA01FRAIN01JP01SINGUK-LON-1US-1AUS-2AUS-2BUS-3AUS-4AUS-5AUS07US08GOV01ca02
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- Oct 06, 2026, 08:09 PM UTC
- Resolved
- Oct 08, 2026, 12:33 AM UTC
- Duration
- 1d 4h
Affected: AP-SYD-1BR01CA01FRAIN01JP01SINGUK-LON-1US-1AUS-2AUS-2BUS-3AUS-4AUS-5AUS07US08GOV01ca02
Timeline · 5 updates
-
investigating Oct 06, 2026, 08:09 PM UTC
We are aware of and actively investigating issues with the cloud scanners plugins set not updating. We will provide periodic updates as our engineers continue working on this issue.
-
investigating Oct 06, 2026, 08:13 PM UTC
The sites will be undergoing temporary maintenance for ~15 minutes. Manual scan launches may need to be reattempted once the window is completed
-
identified Oct 06, 2026, 08:16 PM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
-
identified Oct 06, 2026, 10:03 PM UTC
It has been determined that this issue is superficial and cloud scanner plugin sets are up-to-date.
-
resolved Oct 08, 2026, 12:33 AM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Oct 05, 2026, 02:47 PM UTC
- Resolved
- Oct 05, 2026, 09:40 PM UTC
- Duration
- 6h 52m
Affected: GOV01
Timeline · 6 updates
-
investigating Oct 05, 2026, 02:47 PM UTC
We are aware of and actively investigating issues that are impacting the loading speed of the GUI for certain users. We will provide periodic updates as our engineers continue working on this issue.
-
investigating Oct 05, 2026, 03:47 PM UTC
Our engineering team continues to investigate this issue.
-
investigating Oct 05, 2026, 07:19 PM UTC
Our engineering team continues to investigate this issue.
-
identified Oct 05, 2026, 08:25 PM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
-
monitoring Oct 05, 2026, 08:33 PM UTC
We have implemented a fix for the issue and are monitoring the recovery.
-
resolved Oct 05, 2026, 09:40 PM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2026, 05:18 PM UTC
- Resolved
- Sep 30, 2026, 11:48 PM UTC
- Duration
- 5d 6h
Affected: BR01US-1AUS-2AUS-4AUS-5AUS08GOV01
Timeline · 11 updates
Read the full incident report →
- Detected by Pingoru
- Sep 23, 2026, 03:32 PM UTC
- Resolved
- Oct 06, 2026, 02:37 PM UTC
- Duration
- 12d 23h
Affected: US-2AUS08
Timeline · 4 updates
-
investigating Sep 23, 2026, 03:32 PM UTC
We are aware of and actively investigating latency that is impacting recast rule processing for certain users. We will provide periodic updates as our engineers continue working on this issue.
-
monitoring Sep 23, 2026, 06:46 PM UTC
We have implemented a fix for the issue and are monitoring the recovery.
-
identified Sep 28, 2026, 09:00 AM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
-
resolved Oct 06, 2026, 02:37 PM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
Critical September 19, 2026 - Detected by Pingoru
- Sep 19, 2026, 01:01 AM UTC
- Resolved
- Sep 20, 2026, 02:59 AM UTC
- Duration
- 1d 1h
Affected: USGov1
Timeline · 7 updates
-
investigating Sep 19, 2026, 01:01 AM UTC
We are aware of and actively investigating a degraded ClickHouse cluster that are impacting Orchestration failures for certain users. We will provide periodic updates as our engineers continue working on this issue.
-
investigating Sep 19, 2026, 01:08 AM UTC
We are continuing to investigate this issue.
-
investigating Sep 19, 2026, 03:09 AM UTC
Our engineering team continues to investigate this issue.
-
investigating Sep 19, 2026, 06:14 AM UTC
Our engineering team continues to investigate this issue.
-
identified Sep 19, 2026, 07:16 AM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
-
monitoring Sep 19, 2026, 03:31 PM UTC
We have implemented a fix for the issue and are monitoring the recovery.
-
resolved Sep 20, 2026, 02:59 AM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Sep 18, 2026, 04:13 PM UTC
- Resolved
- Sep 22, 2026, 01:44 PM UTC
- Duration
- 3d 21h
Affected: AP-SYD-1SINGUS-1AUS-2AUS-3AUS08
Timeline · 6 updates
-
investigating Sep 18, 2026, 04:13 PM UTC
We are aware of and actively investigating issues with asset tagging not working for certain users. We will provide periodic updates as our engineers continue working on this issue.
-
investigating Sep 18, 2026, 04:50 PM UTC
We are continuing to investigate this issue.
-
investigating Sep 18, 2026, 05:48 PM UTC
We are continuing to investigate this issue.
-
investigating Sep 18, 2026, 07:09 PM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
-
identified Sep 19, 2026, 01:53 AM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
-
resolved Sep 22, 2026, 01:44 PM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Sep 18, 2026, 10:02 AM UTC
- Resolved
- Sep 18, 2026, 11:26 AM UTC
- Duration
- 1h 23m
Affected: singus-1aus-2aus-2bus-3aus-4aus-5amssp-us-1 (us07)us08ap-syd-1br01ca01frain01jp01uk-lon-1gov01uae01ca02
Timeline · 4 updates
-
investigating Sep 18, 2026, 10:02 AM UTC
We are aware of and actively investigating ingestion issues that are impacting the Azure cloud connector for certain users. We will provide periodic updates as our engineers continue working on this issue.
-
identified Sep 18, 2026, 10:22 AM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
-
monitoring Sep 18, 2026, 10:44 AM UTC
We have implemented a fix for the issue and are monitoring the recovery.
-
resolved Sep 18, 2026, 11:26 AM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Sep 15, 2026, 07:09 AM UTC
- Resolved
- Sep 24, 2026, 12:01 PM UTC
- Duration
- 9d 4h
Affected: EU
Timeline · 5 updates
-
investigating Sep 15, 2026, 07:09 AM UTC
We are currently investigating an issue affecting data normalization for some EU-region customers, which may cause delays in data syncing; we are actively working on a resolution.
-
monitoring Sep 15, 2026, 12:41 PM UTC
A fix has been implemented and we are monitoring the results.
-
identified Sep 17, 2026, 01:37 PM UTC
Following our initial fix, we observed a recurrence of the issue during the monitoring phase. We have re-identified the root cause and our engineering team is actively preparing a new fix to address this. We will provide another update as soon as the secondary fix is ready for deployment.
-
monitoring Sep 23, 2026, 10:46 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 24, 2026, 12:01 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 11, 2026, 07:50 PM UTC
- Resolved
- Sep 13, 2026, 03:52 AM UTC
- Duration
- 1d 8h
Affected: BR01us08br01US08
Timeline · 5 updates
-
investigating Sep 11, 2026, 07:50 PM UTC
We are aware of and actively investigating delays with vulnerability exports for certain users. We will provide periodic updates as our engineers continue working on this issue.
-
investigating Sep 11, 2026, 10:34 PM UTC
Our engineering team continues to investigate this issue.
-
identified Sep 12, 2026, 07:49 AM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
-
monitoring Sep 12, 2026, 01:27 PM UTC
We have implemented a fix for the issue and are monitoring the recovery.
-
resolved Sep 13, 2026, 03:52 AM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Sep 09, 2026, 04:12 AM UTC
- Resolved
- Sep 10, 2026, 12:04 AM UTC
- Duration
- 19h 52m
Affected: mssp-us-1 (us07)us08ca01fra
Timeline · 5 updates
-
investigating Sep 09, 2026, 04:12 AM UTC
We are aware of and actively investigating issue that are impacting login for users. We will provide periodic updates as our engineers continue working on this issue.
-
monitoring Sep 09, 2026, 05:08 AM UTC
We have implemented a fix for the issue and are monitoring the recovery.
-
monitoring Sep 09, 2026, 05:11 AM UTC
We are continuing to monitor for any further issues.
-
monitoring Sep 09, 2026, 09:54 AM UTC
We are continuing to monitor for any further issues.
-
resolved Sep 10, 2026, 12:04 AM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2026, 02:20 PM UTC
- Resolved
- Sep 02, 2026, 11:52 PM UTC
- Duration
- 9h 31m
Affected: US07
Timeline · 3 updates
-
investigating Sep 02, 2026, 02:20 PM UTC
We are aware of and actively investigating scheduled web application scans failing to start for certain users. We will provide periodic updates as our engineers continue working on this issue.
-
identified Sep 02, 2026, 02:20 PM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
-
resolved Sep 02, 2026, 11:52 PM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2026, 12:46 PM UTC
- Resolved
- Sep 03, 2026, 03:44 PM UTC
- Duration
- 1d 2h
Affected: AP-SYD-1BR01CA01IN01JP01SINGUK-LON-1US-1AUS-2AUS-2BUS-3AUS-4AUS-5AUS08
Timeline · 7 updates
-
investigating Sep 02, 2026, 12:46 PM UTC
We are aware of and actively investigating delays with scan scheduling that are impacting certain users. We will provide periodic updates as our engineers continue working on this issue.
-
investigating Sep 02, 2026, 12:59 PM UTC
We are continuing to investigate this issue.
-
investigating Sep 02, 2026, 01:36 PM UTC
We are continuing to investigate this issue.
-
investigating Sep 02, 2026, 02:31 PM UTC
We are continuing to investigate this issue.
-
monitoring Sep 02, 2026, 06:44 PM UTC
We have implemented a fix for the issue and are monitoring the recovery.
-
monitoring Sep 02, 2026, 11:45 PM UTC
We are continuing to monitor for any further issues.
-
resolved Sep 03, 2026, 03:44 PM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2026, 11:21 AM UTC
- Resolved
- Sep 03, 2026, 09:05 AM UTC
- Duration
- 21h 44m
Affected: AE1AU1BR1CA1EU1IN1JP1KR1SG1UK1US1USGov1
Timeline · 5 updates
-
investigating Sep 02, 2026, 11:21 AM UTC
We are aware of and actively investigating scanning issues with Linux machines that are impacting scanning for certain users. We will provide periodic updates as our engineers continue working on this issue.
-
identified Sep 02, 2026, 11:22 AM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
-
monitoring Sep 02, 2026, 01:38 PM UTC
We have implemented a fix for the issue and are monitoring the recovery.
-
monitoring Sep 02, 2026, 02:41 PM UTC
We are continuing to monitor for any further issues.
-
resolved Sep 03, 2026, 09:05 AM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Sep 01, 2026, 04:33 PM UTC
- Resolved
- Sep 02, 2026, 09:07 AM UTC
- Duration
- 16h 34m
Affected: US1
Timeline · 4 updates
-
investigating Sep 01, 2026, 04:33 PM UTC
We are aware of and actively investigating slowness in the UI for certain users. We will provide periodic updates as our engineers continue working on this issue.
-
investigating Sep 01, 2026, 05:07 PM UTC
We are aware of and actively investigating slowness in the UI and API for certain users. We will provide periodic updates as our engineers continue working on this issue.
-
identified Sep 01, 2026, 06:07 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Sep 02, 2026, 09:07 AM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Aug 31, 2026, 12:53 PM UTC
- Resolved
- Sep 01, 2026, 04:27 PM UTC
- Duration
- 1d 3h
Affected: AU1BR1CA1EU1IN1JP1KR1SG1UK1US1USGov1
Timeline · 4 updates
-
investigating Aug 31, 2026, 12:53 PM UTC
We are aware of and actively investigating a delay in Azure sync affecting the ability to see new data for Azure resources for certain users. We will provide periodic updates as our engineers continue working on this issue.
-
monitoring Aug 31, 2026, 04:19 PM UTC
We have implemented a fix for the issue and are monitoring the recovery.
-
monitoring Aug 31, 2026, 07:59 PM UTC
We are continuing to monitor for any further issues.
-
resolved Sep 01, 2026, 04:27 PM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Aug 26, 2026, 01:03 PM UTC
- Resolved
- Aug 28, 2026, 07:26 AM UTC
- Duration
- 1d 18h
Affected: AU1BR1CA1EU1IN1JP1KR1SG1UK1US1
Timeline · 5 updates
-
investigating Aug 26, 2026, 01:03 PM UTC
We are aware of and actively investigating sync delays that are impacting certain Cloud Security users. We will provide periodic updates as our engineers continue working on this issue.
-
investigating Aug 26, 2026, 01:04 PM UTC
We are continuing to investigate this issue.
-
identified Aug 26, 2026, 09:45 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Aug 27, 2026, 07:27 AM UTC
We have implemented a fix for the issue and are monitoring the recovery.
-
resolved Aug 28, 2026, 07:26 AM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2026, 09:18 PM UTC
- Resolved
- Aug 24, 2026, 11:35 AM UTC
- Duration
- 4d 14h
Affected: gov01
Timeline · 4 updates
-
investigating Aug 19, 2026, 09:18 PM UTC
We are aware of and actively investigating agent scans getting stuck in pending or aborting for certain users on Gov01. We will provide periodic updates as our engineers continue working on this issue.
-
monitoring Aug 19, 2026, 09:37 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Aug 20, 2026, 01:46 PM UTC
A fix was implemented and we continue to monitor the results.
-
resolved Aug 24, 2026, 11:35 AM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →
- Detected by Pingoru
- Aug 17, 2026, 06:08 AM UTC
- Resolved
- Aug 18, 2026, 03:34 PM UTC
- Duration
- 1d 9h
Affected: IN01JP01SINGUS-2BUS-4AUS-5Aca02
Timeline · 5 updates
-
identified Aug 17, 2026, 06:08 AM UTC
We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.
-
identified Aug 17, 2026, 08:33 AM UTC
We are continuing to work on a fix for this issue.
-
monitoring Aug 17, 2026, 11:19 AM UTC
We have implemented a fix for the issue and are monitoring the recovery. Customers who downloaded export links generated during the 3 days before this fix and still see a "file has expired" error should re-run the export to get a fresh, working link
-
monitoring Aug 18, 2026, 08:30 AM UTC
We have implemented a fix for the issue and are monitoring the recovery. Customers who downloaded export links generated during the 3 days before this fix and still see a "file has expired" error should re-run the export to get a fresh, working link
-
resolved Aug 18, 2026, 03:34 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 12, 2026, 08:48 PM UTC
- Resolved
- Aug 13, 2026, 03:06 PM UTC
- Duration
- 18h 18m
Affected: US-1A
Timeline · 4 updates
-
investigating Aug 12, 2026, 08:48 PM UTC
We are aware of and actively investigating issues logging in for certain users. We will provide periodic updates as our engineers continue working on this issue.
-
monitoring Aug 12, 2026, 10:43 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Aug 12, 2026, 10:44 PM UTC
We are continuing to monitor for any further issues.
-
resolved Aug 13, 2026, 03:06 PM UTC
The issue has been resolved. We are sorry for the disruption and inconvenience.
Read the full incident report →