Skip to content
Back to TenableIncident Postmortem
Tenable logo

Tenable

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Tenable: vendor-reported major incident on October 1 (tracked 2d 22h)

Oct 1, 02:36 AM → Oct 4, 01:31 AM · 2d 22h · high

Tenable 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 this incident for 2d 22h, closing it on 2026-10-04T01:31:53.452Z.

Duration
2d 22h
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, and therefore cannot describe what users experienced. The incident is known from Tenable's own status page.

Incident timeline

  1. Oct 1, 02:36 AM

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

  2. Oct 1, 02:36 AM

    Status updated: possible issue

  3. Oct 4, 01:31 AM

    PulseWatch closed the incident

Official updates

  1. Oct 1, 02:36 AM

    Tenable 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.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash