DevNet sequencer layer unreachable since ~09:54Z today (2026-08-14), seeking confirmation / ETA

1. #1Peter Davis | ZeroVaultID17-08-2026source ↗
   Hi All,

   
   Since approximately 09:54 am today our validator has had no usable sequencer connectivity on DevNet, and we would appreciate confirmation of whether this is a known network-wide event.
   
   What we observe from our participant node:
   
   1. All fourteen known sequencer connections are in failed-validation with transport errors, cycling reconnect attempts at a steady rate for over twelve hours.
   2. The sequencer public health endpoints we can reach return origin-side HTTP 503 (HTML error pages rather than gRPC responses), and this is consistent across multiple independent operators.
   3. Error composition over a recent five-minute window: several thousand UNAVAILABLE, with zero UNAUTHENTICATED, PERMISSION_DENIED, or RESOURCE_EXHAUSTED. It does not look like an authorization or quota issue on our side.
   4. Sequencer-relayed log lines around onset reported mempool queue full and P2P connectivity not ready (authenticated peers below dissemination quorum), which suggests the sequencer layer's own consensus may have lost quorum.
   5. Our ledger end has been static since onset; host egress from our infrastructure is healthy in the same minutes, so the fault appears remote to us.
   
   Questions:
   
   1. Is this a known DevNet-wide event, and is there an ETA for restoration?
   2. Is any validator-side action recommended, or should operators hold and let reconnection proceed on its own?
   3. Is there a status page or channel where sequencer-layer events are announced, so we can watch that rather than polling?
   
   Happy to share more detailed logs if useful.

    

   Thank you
   
   ZeroVaultID (validator operator)
2. #2v17-08-2026source ↗
   Hi Peter,
   
   We had seen the same from our node on devnet and indeed there seemed an devnet wide event.

   There is an official status page by Canton foundation https://dashboard.canton.foundation/sv-status

   
   It seems the network is in process of recovering at this moment 

   Or you can also use an alternative that our team build at https://superscan-dev.upflam.com/sv-health 
3. #3Peter Davis | ZeroVaultID17-08-2026source ↗
   Hi and sorry for late reply.

    

   I appreciate the link for future reference.

    

   Thanks

    

   Peter