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 3 (tracked 8h 27m)

Nov 3, 02:06 AM → Nov 3, 10:34 AM · 8h 27m · 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 8 hours and 27 minutes, closing it on 2026-11-03T10:34:18.643Z.

Duration
8h 27m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident and therefore cannot describe what users experienced. Information about this incident is based solely on Blockdaemon's status page.

Incident timeline

  1. Nov 3, 02:06 AM

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

  2. Nov 3, 02:06 AM

    Status updated: possible issue

  3. Nov 3, 10:34 AM

    PulseWatch closed the incident

Official updates

  1. Nov 3, 02:06 AM

    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