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 September 28 (tracked 2d 16h)

Sep 28, 10:12 AM → Oct 1, 02:18 AM · 2d 16h · 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 the incident for 2d 16h, from Mon, 28 Sep 2026 10:12:35 GMT to Thu, 01 Oct 2026 02:18:55 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
2d 16h
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:12 AM

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

  2. Sep 29, 04:03 AM

    Status updated: possible issue

  3. Oct 1, 02:18 AM

    PulseWatch closed the incident

Official updates

  1. Sep 28, 10:12 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: fallback