Outage in Tenable

Compliance values not returned due to Max Compliance Output error

Resolved Major
January 26, 2024 - Started over 1 year ago - Lasted 4 days
Official incident page

Need to monitor Tenable outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Tenable, and never miss an outage again.
Start Free Trial

Outage Details

Workaround for current issue: Customers can update any affected policy by updating the Maximum Compliance Output Length value to be not empty. We recommend adding a value of "128000" (no quotes). In SecurityCenter, go to the Policies page. Then choose the affected policy. When that is displayed, choose Advanced from the menu on the left. Scroll down to the "Compliance Output Settings". There, you can add the value of 128000 to the Maximum Compliance Output Length In KB field.
Latest Updates ( sorted recent to last )
RESOLVED over 1 year ago - at 01/31/2024 02:08AM

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

MONITORING over 1 year ago - at 01/31/2024 01:40AM

We are continuing to monitor the recovery.

MONITORING over 1 year ago - at 01/30/2024 05:40PM

We have implemented a fix for the issue and continue monitoring the recovery

MONITORING over 1 year ago - at 01/30/2024 08:44AM

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

MONITORING over 1 year ago - at 01/30/2024 05:46AM

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

IDENTIFIED over 1 year ago - at 01/30/2024 01:44AM

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

IDENTIFIED over 1 year ago - at 01/29/2024 06:20PM

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

IDENTIFIED over 1 year ago - at 01/29/2024 12:17PM

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

IDENTIFIED over 1 year ago - at 01/29/2024 06:31AM

Our engineering team is working on and testing the fix. Meanwhile please use the workaround steps to mitigate the issue.

IDENTIFIED over 1 year ago - at 01/29/2024 01:03AM

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

IDENTIFIED over 1 year ago - at 01/28/2024 12:23AM

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

IDENTIFIED over 1 year ago - at 01/27/2024 06:11AM

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

INVESTIGATING over 1 year ago - at 01/26/2024 11:52PM

Workaround for current issue:

Customers can update any affected policy by updating the Maximum Compliance Output Length value to be not empty.
We recommend adding a value of "128000" (no quotes).


In SecurityCenter, go to the Policies page. Then choose the affected policy. When that is displayed, choose Advanced from the menu on the left. Scroll down to the "Compliance Output Settings". There, you can add the value of 128000 to the Maximum Compliance Output Length In KB field.

Be the First to Know When Vendors Go Down

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 4484 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook