# OpenWAF Status

> Live status of OpenWAF services (website, docs, dashboard, API, MCP server, edge network by region, authoritative DNS,
> Verify challenge, AI Egress). Probed every minute from outside our infrastructure; hosted independently of it.

## Read

- [Current status as Markdown](https://status.openwaf.dev/index.md)
- [Statuspage v2 summary (JSON)](https://status.openwaf.dev/api/v2/summary.json): page, components, unresolved incidents, maintenance, indicator
- [Status indicator only (JSON)](https://status.openwaf.dev/api/v2/status.json)
- [Incidents (JSON)](https://status.openwaf.dev/api/v2/incidents.json) and [unresolved](https://status.openwaf.dev/api/v2/incidents/unresolved.json)
- [Scheduled maintenances (JSON)](https://status.openwaf.dev/api/v2/scheduled-maintenances.json), [upcoming](https://status.openwaf.dev/api/v2/scheduled-maintenances/upcoming.json), [active](https://status.openwaf.dev/api/v2/scheduled-maintenances/active.json)
- [Incident history (Atom)](https://status.openwaf.dev/history.atom), [RSS](https://status.openwaf.dev/history.rss), [maintenance calendar (iCal)](https://status.openwaf.dev/maintenance.ics)

## Notes

- An incident lists the components and locations it affects; a regional or single-product incident is not a global outage.
- Uptime counts major outage minutes plus 0.3 × partial outage minutes as downtime; degraded performance and maintenance are not downtime.
- How it works: https://status.openwaf.dev/about/