Status
Welcome to the Twilio status page. Here you will find real-time information about status of our services.
Twilio Status API
Documentation and Functionality
Basics
The following documentation is provided to let users of the Twilio status page programmatically access various elements on the page. Endpoints are displayed with examples using cURL and our embeded javascript widget (if available).
Javascript Library
A wrapper for the page status api, exposing convenient actions useful for embedding your status anywhere.
https://cdn.statuspage.io/se-v2.js
Summary
Get a summary of the status page, including a status indicator, component statuses, unresolved incidents, and any upcoming or in-progress scheduled maintenances.
https://gpkpyklzq55q.statuspage.io/api/v2/summary.json Click For Example
Status
Get the status rollup for the whole page. This endpoint includes an indicator - one of none, minor, major, or critical, as well as a human description of the blended component status. Examples of the blended status include "All Systems Operational", "Partial System Outage", and "Major Service Outage".
https://gpkpyklzq55q.statuspage.io/api/v2/status.json Click For Example
Components
Get the components for the page. Each component is listed along with its status - one of operational, degraded_performance, partial_outage, or major_outage.
https://gpkpyklzq55q.statuspage.io/api/v2/components.json Click For Example
Incidents
Incidents are the cornerstone of any status page, being composed of many incident updates. Each incident usually goes through a progression of statuses listed below, with an impact calculated from a blend of component statuses (or an optional override).
Status: Investigating, Identified, Monitoring, Resolved, or Postmortem
Impact: None (black), Minor (yellow), Major (orange), or Critical (red)
Unresolved Incidents
Get a list of any unresolved incidents. This endpoint will only return incidents in the Investigating, Identified, or Monitoring state.
https://gpkpyklzq55q.statuspage.io/api/v2/incidents/unresolved.json Click For Example
All Incidents
Get a list of the 50 most recent incidents. This includes all unresolved incidents as described above, as well as those in the Resolved and Postmortem state.
https://gpkpyklzq55q.statuspage.io/api/v2/incidents.json Click For Example
Scheduled Maintenances
Scheduled Maintenances are planned outages, upgrades, or general notices that you're working on infrastructure and disruptions may occurr. A close sibling of Incidents, each usually goes through a progression of statuses listed below, with an impact calculated from a blend of component statuses (or an optional override).
Status: Scheduled, In Progress, Verifying, or Completed
Impact: None (black), Minor (yellow), Major (orange), or Critical (red)
Upcoming Scheduled Maintenances
Get a list of any upcoming maintenances. This endpoint will only return scheduled maintenances still in the Scheduled state.
https://gpkpyklzq55q.statuspage.io/api/v2/scheduled-maintenances/upcoming.json Click For Example
Active Scheduled Maintenances
Get a list of any active maintenances. This endpoint will only return scheduled maintenances in the In Progress or Verifying state.
https://gpkpyklzq55q.statuspage.io/api/v2/scheduled-maintenances/active.json Click For Example
All Scheduled Maintenances
Get a list of the 50 most recent scheduled maintenances. This includes scheduled maintenances as described in the above two endpoints, as well as those in the Completed state.
https://gpkpyklzq55q.statuspage.io/api/v2/scheduled-maintenances.json Click For Example
Subscribers
Subscribers receive incident notifications via email, SMS, or webhook. You can create and remove subscriptions for all upcoming incidents as well as specific incidents using the subscribers api. You can even tune which components a subscriber is interested in.
Page Subscribers
A page subscriber is by default subscribed to all incidents associated with a page.
https://gpkpyklzq55q.statuspage.io/api/v2/subscribers.json Click For Example
Incident Subscribers
When an incident is created, a subscriber can be associated to that incident to receive notifications on updates until the incident is resolved. The incident must be in an unresolved state to subscribe to it.
https://gpkpyklzq55q.statuspage.io/api/v2/subscribers.json Click For Example
Tuning Subscription Components
To tune an existing subscription to add or remove components, submit a PATCH request with the subscriber id and a new list of components.
https://gpkpyklzq55q.statuspage.io/api/v2/subscribers/<subscriber_id>.json Click For Example
Removing Subscriptions
To remove a subscription, submit a DELETE request with the the subscription id.
https://gpkpyklzq55q.statuspage.io/api/v2/subscribers/<subscriber_id>.json Click For Example
Resending a Confirmation Email
To resend a confirmation email for an unconfirmed email subscriber, submit a POST request with the the subscription id.
https://gpkpyklzq55q.statuspage.io/resend_confirmation/<subscriber_id> Click For Example