> For the complete documentation index, see [llms.txt](https://zeebu-1.gitbook.io/zeebu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zeebu-1.gitbook.io/zeebu/protocol/security-and-compliance/risk-mitigation/network-downtime.md). # Network Downtime Zeebu's resilience against network downtime stems from its decentralized architecture and multi-chain strategy. By design, the protocol's operations are distributed across multiple independent nodes, eliminating single points of failure. This structure ensures that Zeebu remains functional unless all underlying blockchains it interacts with experience simultaneous outages – an event unprecedented in the history of major blockchain networks. The protocol's multi-chain approach provides an additional layer of redundancy. By attesting data to multiple blockchain networks, Zeebu creates multiple backups of its operational state. This diversification means that even if one blockchain faces issues, the protocol can continue functioning on others. Given the proven track record of networks like Ethereum, which has maintained near-continuous uptime for over a decade, Zeebu's multi-chain strategy provides a robust defense against potential network disruptions. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://zeebu-1.gitbook.io/zeebu/protocol/security-and-compliance/risk-mitigation/network-downtime.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.