Skip to content
Back to BlockdaemonIncident Postmortem
Blockdaemon logo

Blockdaemon

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Blockdaemon: vendor-reported critical incident on September 23 (tracked 17h 14m)

Sep 23, 03:44 PM → Sep 24, 08:59 AM · 17h 14m · high

Blockdaemon 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 the incident for 17h 14m, from Wed, 23 Sep 2026 15:44:25 GMT to Thu, 24 Sep 2026 08:59:22 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
17h 14m
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 23, 03:44 PM

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

  2. Sep 23, 03:44 PM

    Status updated: possible issue

  3. Sep 24, 08:59 AM

    PulseWatch closed the incident

Official updates

  1. Sep 23, 03: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: fallback