Today we're introducing groups for your status page sections, bringing a new level of organization to your service monitoring. You can now create logical groupings of related services within each section, making your status pages even more structured and easier to navigate.

Why Groups Matter
While sections help organize your status page at a high level, groups provide that extra layer of organization when you need it:
- Bundle microservices: Group your auth service, user service, and payment service under "Core Platform"
- Regional deployments: Organize CDN endpoints or databases by region (US-East, EU-West, APAC)
- Team ownership: Group services by the teams responsible (Platform Team, Data Team, Frontend Team)
- Dependencies: Keep related services together (Redis Cache + Redis Queue + Redis Pub/Sub)
Check out our status page to see groups in action.
Related Articles
Best UptimeRobot Alternatives in 2026: 5 Picks, Priced
UptimeRobot alternatives compared on price, check interval and on-call: Hyperping, Better Stack, Pingdom, Uptime.com and...
Why you need a status page (& what great ones include)
Status pages reduce support tickets by 24% during outages. Learn about automated updates, public vs private pages, and w...
Public vs private status pages [cost analysis, security, compliance, and more]
Public vs private status pages: which builds trust and cuts support tickets by 50%? Compare pros, cons, hybrid options, ...
Introducing the Hyperping Intercom Integration: Reduce Support Tickets with Proactive Status Communication
New Intercom integration automatically shares service status and incident updates directly in your support conversations...




