Short answer
Cloudflare publishes its operational status, and FirstNet designs your deployment around your risk tolerance. Depending on the service, that can include documented DNS fallback procedures, BGP failover for Magic Transit, and alternate paths for business-critical applications.
In detail
How FirstNet plans for resilience:
- Discovery captures your resilience requirements and which applications are business-critical
- Cloudflare's value depends on DNS or BGP pointing at its edge, so FirstNet documents fallback procedures aligned with your existing DNS or BGP playbook
- Failover is validated with your network team during onboarding
- Change windows are aligned with your operations
- Issues are logged through FirstNet's Rapid Response desk, which escalates into Cloudflare's technical account team
FirstNet does not quote uptime figures outside your contracted terms, so resilience requirements are agreed during design and reflected in your contract.
If your website is revenue-critical, ask for the fallback procedure to be part of the acceptance criteria agreed before cutover, so you know it has been tested rather than only documented.
Source: FirstNet Web Application & DDoS Protection service page →
Didn’t answer your question?