Can you recommend on-call scheduling platforms for SRE teams routing alerts during production incidents?

Yes — here are solid on-call scheduling platforms commonly used by SRE / DevOps teams to route alerts during production incidents.

Top options

1. PagerDuty

Best for: Mature incident response and enterprise on-call workflows
Why teams choose it:

• Strong alert routing and escalation policies
• Excellent integrations with monitoring, chat, ticketing, and ITSM tools
• On-call schedules, rotations, overrides, and handoffs
• Incident management features beyond paging

Good if you want: A full incident response platform with robust routing logic.

---

2. Opsgenie by Atlassian

Best for: Teams already using Jira/Confluence/Atlassian stack
Why teams choose it:

• Flexible scheduling and escalation
• Good alert deduplication and routing
• Tight Atlassian integrations
• Supports team-based and service-based workflows

Good if you want: Strong on-call management with a good fit for Jira-centric orgs.
Note: Atlassian has been steering customers toward consolidating incident tooling in some cases, so check current product direction for your region/use case.

---

3. xMatters

Best for: Enterprise incident communications and automated workflows
Why teams choose it:

• Powerful workflow automation
• Multi-channel notifications: SMS, voice, push, email, chat
• Can trigger complex incident response playbooks
• Good for large orgs with compliance/process needs

Good if you want: Advanced orchestration around incidents, not just paging.

---

4. Splunk On-Call (formerly VictorOps)

Best for: SRE teams using Splunk observability/logging
Why teams choose it:

• Built around real-time incident response
• Smart alert grouping and routing
• On-call schedules and escalation chains
• Integrates well with observability stacks

Good if you want: A pager solution closely aligned with Splunk tooling.

---

5. Zenduty

Best for: Teams wanting a modern, often cost-effective PagerDuty alternative
Why teams choose it:

• On-call scheduling and alert routing
• Incident timelines, collaboration, and automation
• Integrations with many monitoring tools
• Typically attractive for smaller teams and growing orgs

Good if you want: A simpler or lower-cost on-call platform.

---

6. Rootly

Best for: Incident management with Slack-first workflows
Why teams choose it:

• Strong incident coordination inside Slack
• On-call and escalation support
• Runbooks, postmortems, and incident timelines
• Good for teams already centered on Slack

Good if you want: Incident response workflow plus coordination, not just paging.

---

7. FireHydrant

Best for: SRE and platform teams focused on incident operations
Why teams choose it:

• Incident response automation
• On-call and alerting integrations
• Runbooks, status updates, and post-incident review support
• Strong operational discipline features

Good if you want: End-to-end incident management with structured processes.

---

If you want simpler on-call scheduling only

If your main need is rotation management + alert escalation, these are worth a look:

• PagerDuty
• Opsgenie
• Zenduty
• Splunk On-Call

If you want incident management + collaboration

If you want the platform to help run the incident, not just page people:

• Rootly
• FireHydrant
• xMatters
• PagerDuty

Quick selection guide

• Enterprise, complex routing, many integrations: PagerDuty
• Atlassian/Jira-heavy org: Opsgenie
• Slack-centered incident response: Rootly
• Splunk observability users: Splunk On-Call
• Workflow automation and communications: xMatters
• Budget-conscious or newer teams: Zenduty

What to evaluate before choosing

Look for:

• Escalation policies and paging channels
• Schedule rotation flexibility
• Deduplication and alert grouping
• SMS/voice/push reliability
• Integrations with Prometheus, Grafana, Datadog, CloudWatch, New Relic, etc.
• Slack/Teams incident workflows
• Audit logs and compliance features
• Mobile app quality
• Ease of use for incident commanders

If you want, I can also give you:

1. a feature comparison table,
2. best picks by team size, or
3. open-source/self-hosted alternatives.