Show the status of the services you depend on, such as AWS, Cloudflare, GitHub, or Stripe, on your status page. Better Stack follows each vendor's public status page, so the row updates on its own when the vendor reports an incident.

Add a third party service

1. Go to Incidents → Status pages → your status page → Structure.
2. Type the vendor's name into a section's Search to add resources dropdown, for example cloudflare.
3. Select the vendor under Third party services. To pick from the full list instead, select Browse all third party services.
4. Choose what the row covers and click Add row.
5. Click Save changes.

Missing a provider?

Let us know at hello@betterstack.com.

Choose what a row covers

Many vendors split their status into groups, such as Cloudflare's data center locations or AWS regions. Pick how much of the vendor to show:

• All of Cloudflare: one row with the vendor's overall status.
• Selected groups: one row for each group you pick. Click Continue, then choose whether each row covers All services in its group or only Selected services.

For AWS, the options are All of AWS and Selected regions and services.

For a vendor without groups, such as Stripe, Selected services adds one row that covers only the services you pick.

Change a row later

Expand the row to change its Public name, Explanation, or Widget type. A row for a group also lets you pick its services under Services shown.

To change anything else, such as the groups or the vendor, open the row's ⋯ menu and select Configure. The dialog opens with the row's current choices. Click Update row, then Save changes.

How status and history work

Each row's status comes from what the vendor reports on its own status page:

• A row for the whole vendor shows the vendor's overall status.
• A row for a group or for selected services is Degraded while any of its services is degraded or down. It shows Downtime only while all of its services are down.

Visitors can expand a row for a group or for selected services to see the status of each service in it, and click a row's name to open the vendor's status page.

Status history goes back to when Better Stack started following the vendor. Choose how much of it to show with the row's Widget type.

Limits

• Visitors can't subscribe to a third party service row, and a vendor's incident doesn't notify your subscribers. To tell them how a vendor's outage affects you, create a status report.
• Add third party services in the status page editor. The status page resources API lists them with the ThirdPartyService resource type but can't create them.