All endpoints are public, read-only, and require no authentication. Requests use GET and return either JSON or a standard syndication feed.
Use the API for automated access instead of scraping the status page. Timestamps in JSON responses are returned in UTC.
Public status pages also support an agent-friendly Markdown representation. Send Accept: text/markdown to the page URL to receive a concise, text-only snapshot.
Public endpoints
Page status
4 endpoints
Use these endpoints to understand the current state of the status page and its services.
The original summary endpoint. New integrations should use the versioned JSON endpoint below.
Example request
curl --request GET 'https://status.nopecha.com/api/v1/summary'
A complete snapshot of the page, including the overall status, components, unresolved incidents, and scheduled maintenance.
Example request
curl --request GET 'https://status.nopecha.com/api/v2/summary.json'
The overall status indicator and a human-readable description for the page.
Example request
curl --request GET 'https://status.nopecha.com/api/v2/status.json'
Every public service and site, including its current status, position, group, and location.
Example request
curl --request GET 'https://status.nopecha.com/api/v2/components.json'
Public endpoints
Incidents
2 endpoints
Read current or historical incident information in a machine-readable format.
Incidents that are currently investigating, identified, or monitoring.
https://status.nopecha.com/api/v2/incidents/unresolved.json
Open response ↗
Example request
curl --request GET 'https://status.nopecha.com/api/v2/incidents/unresolved.json'
The 50 most recent incidents, including resolved incidents and their public updates.
Example request
curl --request GET 'https://status.nopecha.com/api/v2/incidents.json'
Public endpoints
Scheduled maintenance
3 endpoints
Track upcoming, active, and recently completed maintenance windows.
Maintenance events that are still in the scheduled state.
https://status.nopecha.com/api/v2/scheduled-maintenances/upcoming.json
Open response ↗
Example request
curl --request GET 'https://status.nopecha.com/api/v2/scheduled-maintenances/upcoming.json'
Maintenance events currently in progress or being verified.
https://status.nopecha.com/api/v2/scheduled-maintenances/active.json
Open response ↗
Example request
curl --request GET 'https://status.nopecha.com/api/v2/scheduled-maintenances/active.json'
The 50 most recent maintenance events, including completed events.
https://status.nopecha.com/api/v2/scheduled-maintenances.json
Open response ↗
Example request
curl --request GET 'https://status.nopecha.com/api/v2/scheduled-maintenances.json'
Subscribe to incident and maintenance updates with the feed reader of your choice.
Recent public incident updates, with links back to their incident pages.
Example request
curl --request GET 'https://status.nopecha.com/history.rss'
The 50 most recent incidents, with links to their public incident pages.
Example request
curl --request GET 'https://status.nopecha.com/api/v3/incidents.rss'
The 50 most recent incidents in Atom format.
Example request
curl --request GET 'https://status.nopecha.com/api/v3/incidents.atom'
The 50 most recent scheduled maintenance events, including maintenance window end dates.
Example request
curl --request GET 'https://status.nopecha.com/api/v3/maintenance.rss'
The 50 most recent scheduled maintenance events in Atom format.
Example request
curl --request GET 'https://status.nopecha.com/api/v3/maintenance.atom'
Reference
Common status values
ValueMeaning
noneThe overall page is operating normally.
minorThe page has a minor service issue.
majorThe page has a partial service outage.
criticalThe page has a major service outage.
maintenanceOne or more services are under maintenance.
operationalA component is operating normally.
degraded_performanceA component is available with reduced performance.
partial_outageA portion of a component is unavailable.
major_outageA component is substantially or completely unavailable.