Skip to content
Back to ShippoIncident Postmortem
Shippo logo

Shippo

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Shippo: vendor-reported major incident on September 29 (tracked 2h 59m)

Sep 29, 12:55 PM → Sep 29, 03:55 PM · 2h 59m · high

Shippo 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 2h 59m, from Tue, 29 Sep 2026 12:55:54 GMT to Tue, 29 Sep 2026 15:55:29 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
2h 59m
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, 12:55 PM

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

  2. Sep 29, 12:55 PM

    Status updated: possible issue

  3. Sep 29, 03:55 PM

    PulseWatch closed the incident

Official updates

  1. Sep 29, 12:55 PM

    Shippo 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