Skip to content
Back to BlockdaemonIncident Postmortem
Blockdaemon logo

Blockdaemon

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Blockdaemon: vendor-reported major incident on November 2 (tracked 2h 4m)

Nov 2, 12:44 PM → Nov 2, 02:49 PM · 2h 4m · high

Blockdaemon 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 2 hours and 4 minutes, closing tracking on 2026-11-02T14:49:21.010Z.

Duration
2h 4m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident. Therefore, PulseWatch cannot describe what users experienced; information regarding this major outage is based solely on Blockdaemon's own status page.

Incident timeline

  1. Nov 2, 12:44 PM

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

  2. Nov 2, 12:44 PM

    Status updated: possible issue

  3. Nov 2, 02:49 PM

    PulseWatch closed the incident

Official updates

  1. Nov 2, 12:44 PM

    Blockdaemon 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