If you subscribe to the Atmos Pro status feed — in an RSS reader, or piped into a Slack channel alongside your other vendors' status pages — you were getting a fresh "All Systems Operational" post every polling cycle. The feed stamped the current time into each dependency's item, so every poll looked like brand-new items to the reader, even when nothing had changed. The fix makes the feed behave like the
/history.atom feeds you already follow from GitHub, Datadog, and others: an item appears only when there's a real incident.The default feed now reports Atmos Pro's own incidents only. When everything is healthy it's empty and byte-for-byte identical between polls, so your reader sees nothing new and your channel stays quiet until something actually happens. Each incident keeps a stable identity, so it's posted once — not re-posted every minute.
We also split the feeds so you can subscribe to exactly what you want:
https://atmos-pro.com/status/history.atom(or.rss) — Atmos Pro incidentshttps://atmos-pro.com/status/dependencies.atom(or.rss) — active third-party dependency incidents (GitHub, Vercel, Inngest, Neon, Resend, Stripe)
If you already poll
/api/status/feed, it keeps working and now defaults to the Atmos-incidents-only view. Point your alerting at history.atom and it'll page you when there's an incident — and otherwise leave you alone.