Skip to main content
Every public status page exposes a feed of its recent incidents. There is no setup and no recipient list: anyone can subscribe a reader, or pipe the feed into a tool that accepts RSS or Atom.

​
Feed URLs

For a page at status.example.com:
  • Atom: https://status.example.com/feed.atom
  • RSS 2.0: https://status.example.com/feed.rss
Each incident update and maintenance transition is its own entry, newest first.

​
What appears

The feed mirrors what a logged-out visitor sees on the page:
  • Restricted pages serve a feed to clients that pass the page’s access check: an allowed IP, or a JWT sent as a Bearer token or ?token=. Password-protected and sign-in protected pages do not serve a feed to feed readers.
  • Customer-scoped incidents appear only in feeds requested with that customer’s token.

​
Caching

Feeds are cached for one minute and support conditional requests, so readers that poll frequently get a cheap 304 Not Modified between updates.
Use a feed for read-only mirroringA feed is a good fit for piping incident history into an internal tool or an aggregator. For real-time paging, use an on-call or chat integration instead.