Skip to content
Back to HarnessIncident Postmortem
Harness logo

Harness

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Harness: vendor-reported minor incident on September 29 (tracked 5h 56m)

Sep 29, 05:00 PM → Sep 29, 10:56 PM · 5h 56m · medium

Harness reported a minor-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 5h 56m, from Tue, 29 Sep 2026 17:00:13 GMT to Tue, 29 Sep 2026 22:56:28 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
5h 56m
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 29, 05:00 PM

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

  2. Sep 29, 05:00 PM

    Status updated: possible issue

  3. Sep 29, 10:56 PM

    PulseWatch closed the incident

Official updates

  1. Sep 29, 05:00 PM

    Harness 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