Skip to content
PulseWatchOUTAGE.INTEL
Tenable Vulnerability Management logo

Other

Is Tenable Vulnerability Management down right now?

Vendor-reported issueOfficial status last polled Oct 3, 2026 12:55 UTCwww.tenable.com/products/tenable-ioOfficial status page

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

Is Tenable Vulnerability Management down right now?

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

Status as of Oct 3, 2026 12:59 UTC

Vendor-reported issueVendor-reported issue

Tenable Vulnerability Management: vendor reports an issue

As of Oct 3, 2026 12:59 UTC

Tenable Vulnerability Management: Recast Rule 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

Oct 1, 2026 10:42 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 Vulnerability Management.

18

Incident days

12

No recorded incident

380h 11m

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 Vulnerability Management. Hover a day for detail.

Sep 4Sep 9Sep 14Sep 19Sep 24Sep 2901234

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

380h 11m

Recorded duration

Report volume

0 reports in last 24H

12:45 PM04:15 PM07:45 PM11:15 PM02:45 AM06:15 AM09:45 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Tenable Vulnerability Management: vendor-reported major incident on September 28 (tracked 3d 0h)

Sep 28, 10:38 AM → Oct 1, 10:42 AM · 3d 0h · high

Tenable Vulnerability Management reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 3d 0h, from Mon, 28 Sep 2026 10:38:32 GMT to Thu, 01 Oct 2026 10:42:37 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
3d 0h
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Sep 28, 10:38 AM

    The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it

  2. Sep 29, 05:37 AM

    Status updated: possible issue

  3. Oct 1, 10:42 AM

    PulseWatch closed the incident

Official updates

  1. Sep 28, 10:38 AM

    Tenable Vulnerability Management reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.

Reliability

Detected by PulseWatch

30-day uptime

46.7%

90-day uptime

66.1%

Calculated from Tenable Vulnerability Management'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 Vulnerability Management: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Tenable Vulnerability Management or have an alert rule on it can be alerted, labelled vendor-reported.

live

10/1/2026, 11:37:49 AM · 2d 1h

11:37 AM12:59 PM (live)
Detection10/1/2026, 11:37:49 AM · 2d ago

Detected — high severity

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

ResolvedHigh

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

9/28/2026, 10:38:32 AM · 3d 0h

10:38 AM10:42 AM
Detection9/28/2026, 10:38:32 AM · 5d ago

Detected — high severity

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

ResolvedHigh

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

9/23/2026, 4:14:42 PM · 3d 0h

04:14 PM04:17 PM
Detection9/23/2026, 4:14:42 PM · 9d ago

Detected — high severity

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

ResolvedHigh

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

9/21/2026, 11:37:41 AM · 1d 16h

11:37 AM04:32 AM
Detection9/21/2026, 11:37:41 AM · 12d ago

Detected — high severity

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

ResolvedHigh

Tenable Vulnerability Management: the vendor reports a major disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

9/18/2026, 10:09:38 AM · 3d 0h

10:09 AM11:02 AM
Detection9/18/2026, 10:09:38 AM · 15d ago

Detected — high severity

Tenable Vulnerability Management: the vendor reports a major disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Tenable Vulnerability Management 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: Recast Rule 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/products/tenable-io