Third-party vendor monitors

Aggregate public status and incident feeds from cloud and SaaS vendors your stack depends on—alongside your own checks

Exemplar

How this capability fits the Exemplar platform—not a standalone point tool, but part of how your org runs production and talks about it.

Why Exemplar

Most production incidents are a mix of your code and a dependency—but vendor status lives in fifteen browser tabs, so teams misdiagnose or over-rotate.

Exemplar pulls public vendor signals into the same surface as your first-party checks so you answer “is it us or them?” faster.

What Exemplar delivers

Curated ingestion of public status and incident feeds from major cloud and SaaS providers, shown alongside your own uptime and health data.

Mapping from vendor incidents to the components and services you define in Exemplar, so impact is legible to engineering and leadership.

How teams use it

Enable the vendor feeds you depend on in the console; attach them to catalog components or logical groupings your teams already recognize.

Use the unified view during triage, then fold notable vendor events into status board updates and incident narratives without copy-pasting from vendor sites.

Capability checklist

Ingest public status and incident feeds—examples include hyperscalers (AWS, GCP, Azure), GitHub, Datadog, Cloudflare, Stripe, and other SaaS your teams rely on

Single view of third-party outages that may impact your services—without juggling each vendor's status site

Tie external incidents to your components, subscribers, and internal alerting

Public beta with a free tier for core vendor feeds

Developer guide

Official documentation on docs.exemplar.dev for this capability.

Open developer guide