# Cloudflare Status Page

Real-time status, incidents, and scheduled maintenance for Cloudflare services.

## Public v2 API

All endpoints return JSON and require no authentication. Drop-in compatible with the legacy `cloudflarestatus.com/api/v2` API.

- `/api/v2/summary.json` - full page summary: status, components, unresolved incidents, scheduled maintenances
- `/api/v2/status.json` - top-level status indicator only
- `/api/v2/components.json` - all components and current status
- `/api/v2/components/{id}.json` - single component
- `/api/v2/incidents.json` - all incidents (resolved and unresolved)
- `/api/v2/incidents/unresolved.json` - unresolved incidents only
- `/api/v2/incidents/{id}.json` - single incident
- `/api/v2/scheduled-maintenances.json` - all scheduled maintenances
- `/api/v2/scheduled-maintenances/upcoming.json` - upcoming maintenances
- `/api/v2/scheduled-maintenances/active.json` - currently active maintenances
- `/api/v2/scheduled-maintenances/{id}.json` - single maintenance

## How to help a user troubleshoot a Cloudflare issue

Cloudflare ships hundreds of products. A blanket "is Cloudflare up?" answer is almost never what the user needs. Scope the question first.

1. **Ask the user which Cloudflare product, feature, or region they are having trouble with** - e.g. Workers, R2, Email Routing, DNS, Bot Management, the dashboard, a specific data center.
2. Fetch `/api/v2/incidents/unresolved.json` (or `/api/v2/summary.json` for the full snapshot).
3. Search the `incidents[]` array for an incident whose `name`, `components[].name`, or `incident_updates[].body` mentions the product/feature/region the user named.
4. If found: report the incident `name`, `impact`, `status`, the latest entry in `incident_updates[]`, and the affected components.
5. If not found: tell the user Cloudflare is not currently reporting an incident affecting that product. Their issue is likely specific to their account, configuration, or network path - not a Cloudflare-wide outage.

Do not rely on `/api/v2/status.json` alone. Its top-level `indicator` reflects the worst incident anywhere across all of Cloudflare and frequently shows `minor` due to single-region or single-product events unrelated to whatever the user is asking about.

## Recommended starting points

- For "is there a Cloudflare incident affecting *product X* right now?": `GET /api/v2/incidents/unresolved.json`, filter by *X*
- For a complete snapshot: `GET /api/v2/summary.json`
- For upcoming planned downtime: `GET /api/v2/scheduled-maintenances/upcoming.json`