Badges and feeds
Embed a live status badge in a README or dashboard, and subscribe to a status page's incident and maintenance announcements over RSS or JSON Feed.
Badges and feeds
Every published status page exposes a small badge image and a feed of its announcements — no account or authentication needed to fetch either.
Status badge
https://<slug>.status.uptimehunt.io/badge.svg
A flat SVG badge showing the page's overall status, in the same style as CI badges you're used to embedding. Drop it straight into a README:
[](https://<slug>.status.uptimehunt.io/)To badge a single component instead of the whole page, add its id — find each component's id in the status page editor's Components tab:
https://<slug>.status.uptimehunt.io/badge.svg?component=<component_id>The badge is cached for a short time (about a minute), so it won't hammer your status page on every README render.
RSS and JSON feeds
Subscribe to a page's incident updates and maintenance announcements in whichever format your reader supports:
https://<slug>.status.uptimehunt.io/feed.xml— RSS 2.0https://<slug>.status.uptimehunt.io/feed.json— JSON Feed 1.1
Both carry the same entries — published incident updates and maintenance announcements, newest first, capped at the most recent 50 — just in different formats. There's one feed per page, not one per component.
What's in the feed
Only what's manually published shows up: incident status updates (investigating → identified → monitoring → resolved) and maintenance windows. Routine status flips — a component going up or down on its own — are not feed entries; that's what the badge and the page itself are for.
Related Documentation
Maintenance windows
Schedule planned maintenance on a status page and automatically suppress alerts for the services and cron jobs it covers, for exactly as long as the window runs.
Global Probe Network
UptimeHunt's global probe network monitors your services from multiple geographic locations worldwide. Learn how probes work, view the fleet, and run your own.