dockerstatus.com APIdockerstatus.com ↗
Monitor Docker's real-time service health, incident history, and RSS feed via the dockerstatus.com API. 5 endpoints covering all services and past incidents.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/2abe8c54-9d74-40c0-ac54-5b470c179510/get_overall_status' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns the overall system status banner (e.g., 'Operational') and the last-updated timestamp from Docker's status page.
No input parameters required.
{
"type": "object",
"fields": {
"status": "string indicating overall system state (e.g. 'Operational')",
"updated_at": "string ISO 8601 timestamp of last update",
"status_code": "integer status code (100 = operational)"
},
"sample": {
"data": {
"status": "Operational",
"updated_at": "2026-05-14T05:30:24.085Z",
"status_code": 100
},
"status": "success"
}
}About the dockerstatus.com API
The Docker Status API exposes 5 endpoints that surface Docker's current platform health, per-service operational status, and full incident history as reported on dockerstatus.com. The get_all_services_status endpoint returns every Docker service with nested container-level status codes, while get_incident_history provides a timestamped update timeline for each past incident, filterable by component or container ID.
Service Health Data
The get_overall_status endpoint returns a single-string system state (e.g., 'Operational') alongside an ISO 8601 updated_at timestamp and a numeric status_code where 100 signals fully operational. For per-service detail, get_all_services_status returns every service with its id, name, status, updated timestamp, and a containers array — each container carrying its own id, name, status, status_code, and updated fields. This lets you distinguish, for example, whether a regional container within Docker Hub Registry is degraded while the top-level service shows operational.
Querying a Single Service
When you only care about one service, get_service_status accepts either service_id or service_name (case-insensitive). At least one parameter is required. The response shape is identical to a single entry from get_all_services_status, including the nested containers array, so you can slot it into the same parsing logic.
Incident History and RSS Feed
get_incident_history returns past incidents with a full updates array — each update includes a timestamp, status, and message — plus locations and components arrays that name the affected parts of Docker's infrastructure. You can scope results by passing a component_id or container_id filter. For teams that prefer feed-based monitoring, get_rss_feed returns RFC 2822-dated RSS items with HTML-formatted description fields and direct link URLs to each incident's detail page on dockerstatus.com.
- Alert on-call engineers when
get_overall_statusreturns a non-operationalstatus_code - Build a dashboard that polls
get_all_services_statusto display container-level health per Docker region - Integrate
get_service_statusinto a CI pipeline to gate deployments when Docker Hub Registry is degraded - Populate a post-mortem database by ingesting
get_incident_historywith its timestampedupdatesarray - Filter
get_incident_historybycomponent_idto audit how often a specific Docker service has experienced incidents - Ingest
get_rss_feedinto a Slack bot or ticketing system for incident notifications as they are published
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Docker have an official developer API for status data?+
What does the `containers` field in service responses actually represent?+
containers are sub-components or regional breakdowns within a service — not Docker containers in the runtime sense. Each entry has its own id, name, status, status_code, and updated timestamp, so you can detect partial degradation (e.g., one region affected) even when the parent service status shows operational.Can I filter incident history by date range?+
get_incident_history supports filtering by component_id or container_id but does not accept date range parameters. The response includes a human-readable date field and ISO timestamps in each updates entry, so client-side filtering by date is straightforward. You can fork this API on Parse and revise it to add a date range filter endpoint.Does the API expose historical uptime percentages or SLA metrics?+
How fresh is the data from `get_overall_status`?+
updated_at field in the response carries the ISO 8601 timestamp of the last update as reported by dockerstatus.com. The freshness of data reflects when Docker last updated their status page, not a fixed polling interval. For time-sensitive monitoring, compare updated_at against your own request time to detect staleness.