История сбоев Tenable

1. 8 июля 2026 г. в 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 июля 2026 г. в 18:12 UTCmonitoring

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

3. 9 июля 2026 г. в 01:53 UTCresolved

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

Автоматический перевод официального обновления инцидента.

1. 1 июля 2026 г. в 11:30 UTCinvestigating

   We are currently investigating this issue.

2. 1 июля 2026 г. в 11:35 UTCinvestigating

   We are continuing to investigate this issue.

3. 2 июля 2026 г. в 07:52 UTCmonitoring

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

4. 2 июля 2026 г. в 08:57 UTCresolved

   This incident has been resolved.

Автоматический перевод официального обновления инцидента.

1. 24 июня 2026 г. в 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 июня 2026 г. в 07:53 UTCresolved

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

Автоматический перевод официального обновления инцидента.

1. 23 июня 2026 г. в 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 июня 2026 г. в 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 июня 2026 г. в 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 июня 2026 г. в 10:47 UTCresolved

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

Автоматический перевод официального обновления инцидента.

1. 16 июня 2026 г. в 12:28 UTCinvestigating

   We are currently investigating this issue.

2. 16 июня 2026 г. в 14:25 UTCidentified

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

3. 16 июня 2026 г. в 20:54 UTCidentified

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

4. 17 июня 2026 г. в 07:39 UTCmonitoring

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

5. 17 июня 2026 г. в 13:33 UTCresolved

   This incident has been resolved.

Автоматический перевод официального обновления инцидента.

1. 10 июня 2026 г. в 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 июня 2026 г. в 18:35 UTCmonitoring

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

3. 10 июня 2026 г. в 19:16 UTCresolved

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

Автоматический перевод официального обновления инцидента.

1. 5 июня 2026 г. в 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 июня 2026 г. в 17:41 UTCinvestigating

   Our engineering team continues to investigate this issue.

3. 5 июня 2026 г. в 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 июня 2026 г. в 23:14 UTCmonitoring

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

5. 8 июня 2026 г. в 08:26 UTCresolved

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

Автоматический перевод официального обновления инцидента.

1. 5 июня 2026 г. в 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 июня 2026 г. в 09:02 UTCmonitoring

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

3. 5 июня 2026 г. в 10:55 UTCresolved

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

Автоматический перевод официального обновления инцидента.

1. 4 июня 2026 г. в 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 июня 2026 г. в 07:14 UTCmonitoring

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

3. 4 июня 2026 г. в 14:02 UTCresolved

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

Автоматический перевод официального обновления инцидента.

1. 31 мая 2026 г. в 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 мая 2026 г. в 16:41 UTCinvestigating

   We are continuing to investigate this issue.

3. 1 июня 2026 г. в 12:42 UTCmonitoring

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

4. 2 июня 2026 г. в 14:00 UTCresolved

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

Автоматический перевод официального обновления инцидента.

1. 28 мая 2026 г. в 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 мая 2026 г. в 13:47 UTCidentified

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

3. 28 мая 2026 г. в 16:02 UTCresolved

   This incident has been resolved.

Автоматический перевод официального обновления инцидента.

1. 28 мая 2026 г. в 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.

Автоматический перевод официального обновления инцидента.

1. 20 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 20:58 UTCmonitoring

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

4. 21 мая 2026 г. в 11:55 UTCresolved

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

Автоматический перевод официального обновления инцидента.

1. 13 мая 2026 г. в 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 мая 2026 г. в 13:10 UTCinvestigating

   We are continuing to investigate this issue.

3. 13 мая 2026 г. в 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 мая 2026 г. в 17:10 UTCresolved

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

Автоматический перевод официального обновления инцидента.

1. 11 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 17:31 UTCresolved

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

Автоматический перевод официального обновления инцидента.

1. 7 мая 2026 г. в 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 мая 2026 г. в 21:50 UTCresolved

   This incident has been resolved.

Автоматический перевод официального обновления инцидента.

1. 29 апреля 2026 г. в 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 апреля 2026 г. в 20:59 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 апреля 2026 г. в 23:17 UTCmonitoring

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

4. 30 апреля 2026 г. в 13:22 UTCresolved

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

Автоматический перевод официального обновления инцидента.

1. 28 апреля 2026 г. в 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 апреля 2026 г. в 00:15 UTCmonitoring

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

3. 30 апреля 2026 г. в 14:13 UTCresolved

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

Автоматический перевод официального обновления инцидента.

1. 28 апреля 2026 г. в 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 апреля 2026 г. в 07:23 UTCmonitoring

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

3. 30 апреля 2026 г. в 09:31 UTCresolved

   This incident has been resolved.

Автоматический перевод официального обновления инцидента.

1. 28 апреля 2026 г. в 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 апреля 2026 г. в 13:03 UTCinvestigating

   Our engineering team continues to investigate this issue.

3. 29 апреля 2026 г. в 07:48 UTCresolved

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

Автоматический перевод официального обновления инцидента.