Skip to content
Back to ButtondownIncident Postmortem
Buttondown logo

Buttondown

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Buttondown: vendor-reported critical incident on November 7 (tracked 1h 20m)

Nov 7, 12:14 AM → Nov 7, 01:34 AM · 1h 20m · high

Buttondown reported a critical-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 1 hour and 20 minutes, closing it on 2026-11-07T01:34:44.273Z.

Duration
1h 20m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, and therefore cannot describe what users experienced. The incident is known from Buttondown's own status page, which declared a critical impact.

Incident timeline

  1. Nov 7, 12:14 AM

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

  2. Nov 7, 12:14 AM

    Status updated: possible issue

  3. Nov 7, 01:34 AM

    PulseWatch closed the incident

Official updates

  1. Nov 7, 12:14 AM

    Buttondown 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