Skip to content
PulseWatchOUTAGE.INTEL
Tenable logo

Other

Is Tenable down right now?

Vendor-reported issueOfficial status last polled Sep 28, 2026 10:13 UTCwww.tenable.comOfficial status page

Are you on the Tenable team and see something inaccurate? Report it to us. We respond within one business day.

Is Tenable down right now?

Vendor-reported issue. Tenable: Tenable Vulnerability Management: Scan Processing Delays Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

Status as of Sep 28, 2026 10:30 UTC

Vendor-reported issueVendor-reported issue

Tenable: vendor reports an issue

As of Sep 28, 2026 10:30 UTC

Tenable Vulnerability Management: Scan Processing Delays Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

0

Last incident

Sep 26, 2026 16:02 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

Vendor-reported

An official notice is available; independent agreement is unproven.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Tenable.

18

Incident days

12

No recorded incident

365h 31m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Tenable. Hover a day for detail.

Aug 30Sep 4Sep 9Sep 14Sep 19Sep 2401234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

18

Days with incidents

2 incidents

Busiest day

365h 31m

Recorded duration

Report volume

0 reports in last 24H

10:30 AM02:00 PM05:30 PM09:00 PM12:30 AM04:00 AM07:30 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Tenable outage on September 23 A 3-day disruption

Sep 23, 04:02 PM → Sep 26, 04:02 PM · 3d 0h · high

A high-severity incident affecting Tenable services was detected on September 23, 2026. This disruption was identified through automated monitoring and vendor status page updates. Services were fully restored on September 26, 2026.

Peak reports
0
in 15 min
Total reports
0
during outage
Duration
3d 0h
until recovery

Impact

This incident involved a high-severity disruption to Tenable services over a period of three days. The service experienced an outage starting on September 23, 2026, and was resolved on September 26, 2026. During this period, automated monitoring indicated a significant impact on the service's availability. No user-reported data was collected for this incident.

Outage timeline

  1. Sep 23, 04:02 PM

    PulseWatch detected the incident from automated vendor and probe signals (high severity)

  2. Sep 24, 05:36 AM

    Status updated: possible issue

  3. Sep 26, 04:02 PM

    Signals cleared — incident resolved

Official updates

  1. Sep 23, 04:02 PM

    Tenable status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals.

Reliability

Detected by PulseWatch

30-day uptime

47.4%

90-day uptime

71.7%

Calculated from Tenable's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
Possible issueHigh

Tenable: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Tenable or have an alert rule on it can be alerted, labelled vendor-reported.

live

9/28/2026, 10:12:35 AM · 17 min

10:12 AM10:30 AM (live)
Detection9/28/2026, 10:12:35 AM · 17m ago

Detected — high severity

Tenable: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Tenable or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedHigh

Tenable: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Tenable or have an alert rule on it can be alerted, labelled vendor-reported.

9/23/2026, 4:02:37 PM · 3d 0h

04:02 PM04:02 PM
Detection9/23/2026, 4:02:37 PM · 4d ago

Detected — high severity

Tenable: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Tenable or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedMedium

Tenable: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/21/2026, 11:36:52 AM · 1d 16h

11:36 AM04:31 AM
Detection9/21/2026, 11:36:52 AM · 6d ago

Detected — medium severity

Tenable: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedHigh

Tenable: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Tenable or have an alert rule on it can be alerted, labelled vendor-reported.

9/18/2026, 10:07:17 AM · 3d 0h

10:07 AM11:02 AM
Detection9/18/2026, 10:07:17 AM · 10d ago

Detected — high severity

Tenable: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Tenable or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedHigh

Tenable: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Tenable or have an alert rule on it can be alerted, labelled vendor-reported.

9/15/2026, 7:13:48 AM · 3d 0h

07:13 AM08:02 AM
Detection9/15/2026, 7:13:48 AM · 13d ago

Detected — high severity

Tenable: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Tenable or have an alert rule on it can be alerted, labelled vendor-reported.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Tenable enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Vendor-reported issue
Monitoring
Vendor-reported issue: Tenable Vulnerability Management: Scan Processing Delays. Affected scope is described in the vendor notice; service-wide impact is not established.
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

www.tenable.com