Cronologia delle interruzioni di Tenable

1. 8 luglio 2026 alle ore 17:30 UTCinvestigating

   We are aware of and actively investigating HTTP 522 responses when attempting to log into Fedcloud. We will provide periodic updates as our engineers continue working on this issue.

2. 8 luglio 2026 alle ore 18:12 UTCmonitoring

   We have implemented a fix for this issue and are monitoring the recovery.

3. 9 luglio 2026 alle ore 01:53 UTCresolved

   The issue has been resolved. We are sorry for the disruption and inconvenience.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 1 luglio 2026 alle ore 11:30 UTCinvestigating

   We are currently investigating this issue.

2. 1 luglio 2026 alle ore 11:35 UTCinvestigating

   We are continuing to investigate this issue.

3. 2 luglio 2026 alle ore 07:52 UTCmonitoring

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

4. 2 luglio 2026 alle ore 08:57 UTCresolved

   This incident has been resolved.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 24 giugno 2026 alle ore 07:37 UTCinvestigating

   We are aware of and actively investigating asset page load failure for certain users. We will provide periodic updates as our engineers continue working on this issue.

2. 24 giugno 2026 alle ore 07:53 UTCresolved

   The issue has been resolved. We are sorry for the disruption and inconvenience.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 23 giugno 2026 alle ore 20:18 UTCinvestigating

   We are aware of and actively investigating the inability to login to the site for certain users. We will provide periodic updates as our engineers continue working on this issue.

2. 23 giugno 2026 alle ore 21:47 UTCidentified

   We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.

3. 24 giugno 2026 alle ore 07:45 UTCidentified

   Our cloud provider has identified the cause of the problem and is working to implement a fix for the issue.

4. 24 giugno 2026 alle ore 10:47 UTCresolved

   The issue has been resolved. We are sorry for the disruption and inconvenience.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 16 giugno 2026 alle ore 12:28 UTCinvestigating

   We are currently investigating this issue.

2. 16 giugno 2026 alle ore 14:25 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 16 giugno 2026 alle ore 20:54 UTCidentified

   Our engineering team is continuing to work on a fix for this issue.

4. 17 giugno 2026 alle ore 07:39 UTCmonitoring

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

5. 17 giugno 2026 alle ore 13:33 UTCresolved

   This incident has been resolved.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 10 giugno 2026 alle ore 18:05 UTCinvestigating

   We are aware of and actively investigating GUI issues that are impacting menus being displayed for certain users. We will provide periodic updates as our engineers continue working on this issue.

2. 10 giugno 2026 alle ore 18:35 UTCmonitoring

   We have implemented a fix for the issue and are monitoring the recovery.

3. 10 giugno 2026 alle ore 19:16 UTCresolved

   The issue has been resolved. We are sorry for the disruption and inconvenience.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 5 giugno 2026 alle ore 13:18 UTCinvestigating

   We are aware of and actively investigating issues with creating and viewing scans for certain users. We will provide periodic updates as our engineers continue working on this issue.

2. 5 giugno 2026 alle ore 17:41 UTCinvestigating

   Our engineering team continues to investigate this issue.

3. 5 giugno 2026 alle ore 20:25 UTCidentified

   We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.

4. 5 giugno 2026 alle ore 23:14 UTCmonitoring

   We have implemented a fix for the issue and are monitoring the recovery.

5. 8 giugno 2026 alle ore 08:26 UTCresolved

   The issue has been resolved. We are sorry for the disruption and inconvenience.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 5 giugno 2026 alle ore 07:22 UTCinvestigating

   We are aware of and actively investigating issues with creating and viewing scans for certain users. We will provide periodic updates as our engineers continue working on this issue.

2. 5 giugno 2026 alle ore 09:02 UTCmonitoring

   We have implemented a fix for the issue and are monitoring the recovery.

3. 5 giugno 2026 alle ore 10:55 UTCresolved

   The issue has been resolved. We are sorry for the disruption and inconvenience.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 4 giugno 2026 alle ore 06:57 UTCinvestigating

   We are aware of and actively investigating the issue of stale Cloud Security Data and stale Licensed Asset Count within Tenable One that are impacting certain users. We will provide periodic updates as our engineers continue working on this issue.

2. 4 giugno 2026 alle ore 07:14 UTCmonitoring

   We have implemented a fix for the issue and are monitoring the recovery.

3. 4 giugno 2026 alle ore 14:02 UTCresolved

   The issue has been resolved. We are sorry for the disruption and inconvenience.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 31 maggio 2026 alle ore 03:13 UTCinvestigating

   We are aware of and actively investigating an issue with scan processing delays. We will provide periodic updates as our engineers continue working on this issue.

2. 31 maggio 2026 alle ore 16:41 UTCinvestigating

   We are continuing to investigate this issue.

3. 1 giugno 2026 alle ore 12:42 UTCmonitoring

   We have implemented a fix for the issue and are monitoring the recovery.

4. 2 giugno 2026 alle ore 14:00 UTCresolved

   The issue has been resolved. We are sorry for the disruption and inconvenience.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 28 maggio 2026 alle ore 13:46 UTCinvestigating

   We are aware of and actively investigating file validation errors that are impacting WAS API scans for certain users. We will provide periodic updates as our engineers continue working on this issue.

2. 28 maggio 2026 alle ore 13:47 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 28 maggio 2026 alle ore 16:02 UTCresolved

   This incident has been resolved.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 28 maggio 2026 alle ore 19:11 UTCresolved

   Between 3:00PM UTC May 27 2026 to 5:00PM UTC May 28 2026 UTC, certain users could have experienced incorrect VPR scores calculated to the feed. The incorrect scores that may have been populated during that time are being corrected but any exports taken may still be incorrect. The underlying issue has been resolved and corrective actions are being taken to correct the affected data over the next day. We are sorry for the disruption and inconvenience.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 20 maggio 2026 alle ore 19:07 UTCinvestigating

   We are aware of and actively investigating issues with DNS resolution failures for checks related to log4j plugins for certain users. We will provide periodic updates as our engineers continue working on this issue.

2. 20 maggio 2026 alle ore 19:53 UTCidentified

   We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.

3. 20 maggio 2026 alle ore 20:58 UTCmonitoring

   We have implemented a fix for the issue and are monitoring the recovery.

4. 21 maggio 2026 alle ore 11:55 UTCresolved

   The issue has been resolved. We are sorry for the disruption and inconvenience.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 13 maggio 2026 alle ore 13:09 UTCinvestigating

   We are aware of and actively investigating the inability for users to access the Attack Path: Top Attack Paths page in Tenable One. We will provide periodic updates as our engineers continue working on this issue.

2. 13 maggio 2026 alle ore 13:10 UTCinvestigating

   We are continuing to investigate this issue.

3. 13 maggio 2026 alle ore 14:04 UTCidentified

   We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.

4. 13 maggio 2026 alle ore 17:10 UTCresolved

   The issue has been resolved. We are sorry for the disruption and inconvenience.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 11 maggio 2026 alle ore 14:51 UTCinvestigating

   We are aware of and actively investigating issues with new domains added in the MSSP portal not propagating to child containers for certain users. We will provide periodic updates as our engineers continue working on this issue.

2. 11 maggio 2026 alle ore 14:52 UTCidentified

   We have identified the cause of the problem. Our engineering team is working to implement a fix for the issue.

3. 11 maggio 2026 alle ore 17:31 UTCresolved

   The issue has been resolved. We are sorry for the disruption and inconvenience.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 7 maggio 2026 alle ore 19:38 UTCinvestigating

   We are aware of and actively investigating delays for asset and finding ingestion for certain users. We will provide periodic updates as our engineers continue working on this issue.

2. 7 maggio 2026 alle ore 21:50 UTCresolved

   This incident has been resolved.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 29 aprile 2026 alle ore 20:16 UTCinvestigating

   We are aware of and actively investigating Plugins appearing as 'unknown'. We will provide periodic updates as our engineers work on this issue.

2. 29 aprile 2026 alle ore 20:59 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 aprile 2026 alle ore 23:17 UTCmonitoring

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

4. 30 aprile 2026 alle ore 13:22 UTCresolved

   The issue has been resolved. We are sorry for the disruption and inconvenience.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 28 aprile 2026 alle ore 23:21 UTCinvestigating

   We are aware of and actively investigating service degradation that is impacting scan performance for certain users. We will provide periodic updates as our engineers continue working on this issue.

2. 29 aprile 2026 alle ore 00:15 UTCmonitoring

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

3. 30 aprile 2026 alle ore 14:13 UTCresolved

   The issue has been resolved. We are sorry for the disruption and inconvenience.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 28 aprile 2026 alle ore 11:38 UTCinvestigating

   We have identified an issue affecting automatic connector syncs for customers in the EU Region. Our engineers are on the case and investigating the root cause.

2. 29 aprile 2026 alle ore 07:23 UTCmonitoring

   We have implemented a fix for the issue and are monitoring the recovery.

3. 30 aprile 2026 alle ore 09:31 UTCresolved

   This incident has been resolved.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 28 aprile 2026 alle ore 08:18 UTCinvestigating

   We are aware of and actively investigating scan delays that are impacting Oracle Cloud Infrastructure (OCI) customers for certain users. We will provide periodic updates as our engineers continue working on this issue.

2. 28 aprile 2026 alle ore 13:03 UTCinvestigating

   Our engineering team continues to investigate this issue.

3. 29 aprile 2026 alle ore 07:48 UTCresolved

   The issue has been resolved. We are sorry for the disruption and inconvenience.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.