Feature

Status Page & Incident Communication

Public health status, incidents, and history.

14 providers 76 APIs 13 declared variants

A public status page reports current health, incidents, and maintenance windows, often with its own feed or API. Lets integrators distinguish their bug from the provider’s outage.

14 API providers on the APIs.io network offer status page & incident communication. The highest-rated are Dolby.io, MobileAPI.dev, PagerDuty, PolyAPI, Bringg.

Providers

Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.

Exemplar 1 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
Thin 4 Limited public surface area

What Providers Actually Declared

This feature is a canonical term. These are the free-text strings providers wrote in their own apis.yml that map onto it.

Customer Alerts and Service StatusStatus Page and UptimeStatus PagesStatus Pages (external up to 250/500 subscribers by tier)Status page at status.blockdaemon.com with per-component healthStatus page at status.crates.io reporting crates.io and docs.rs uptimeStatus page at status.kushkipagos.com and support knowledge base at soporte.kushkipagos.comStatus page tracking core services and regional infrastructureStatus pages (public + internal)Status pages built-in (Essentials+)StatusPage at valighthouse.statuspage.ioStatuspage at status.bringg.com with per-region component status across 13 components (Auth, API, Customer Experience, Delivery Partners, Dispatch, Driver App, Geolocation, Infrastructure, Inventory, Notifications, Planning, Reporting, Billing)System Health Status Page

Scroll for all 13