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 22 (tracked 21h 50m)

Sep 22, 05:49 PM → Sep 23, 03:39 PM · 21h 50m · 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 21h 50m, from Tue, 22 Sep 2026 17:49:23 GMT to Wed, 23 Sep 2026 15:39:24 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
21h 50m
tracked by PulseWatch

Impact

This high-severity incident affected the Blockdaemon service for approximately 21 hours and 50 minutes, from September 22, 2026, at 17:49 UTC to September 23, 2026, at 15:39 UTC. During this period, automated monitoring systems indicated a disruption to the service. No user-reported data was collected for this incident, and therefore, no specific user-reported features, regions, or issue types can be identified.

Incident timeline

  1. Sep 22, 05:49 PM

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

  2. Sep 23, 05:24 AM

    Status updated: possible issue

  3. Sep 23, 03:39 PM

    PulseWatch closed the incident

Official updates

  1. Sep 22, 05:49 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