Is xMatters Down? How to Check xMatters Status Right Now

Check current xMatters status: statusfield.com/services/xmatters

Slug verified live 2026-09-21 (HTTP 200 from statusfield.com/services/xmatters).

xMatters routes the on-call alerts and incident escalations that tell your team something is broken. That creates an uncomfortable dependency: if xMatters goes down, the tool you rely on to find out about outages becomes part of the outage. Pages don't fire, escalations don't trigger, and your team can be sitting in the dark on a real incident with no idea it's happening.

Here's how to check the current status, spot what's actually broken, and make sure a failure in your incident management layer doesn't become the incident.

Is xMatters Down Right Now?

The fastest way to check: View live xMatters status on Statusfield →

Statusfield monitors xMatters continuously and shows real-time status for the platform's core services — alert delivery, on-call scheduling, integrations, and the admin console. Updated every 5 minutes.

How to Check xMatters Status

1. Statusfield (recommended for DevOps and IT teams) statusfield.com/services/xmatters gives you real-time xMatters status with incident history, independent of xMatters' own infrastructure. That independence matters here more than almost anywhere else: if xMatters is the thing that's down, you need a status signal that doesn't depend on xMatters to reach you.

2. xMatters' Official Status Page xMatters maintains its own status page. Useful as a first check, but it reflects what xMatters chooses to post and how fast — and if the outage is severe enough, the same infrastructure issue can affect how quickly that page gets updated too.

3. Test a Manual Page If you suspect an issue, send a manual test page to an on-call engineer you can reach by another channel (phone, Slack DM). A page that never arrives — or arrives minutes late — confirms a real delivery problem even if the status page hasn't caught up yet.

4. DevOps and SRE community channels Search "xMatters down" on Reddit's r/sysadmin, r/devops, or industry Slack/Discord communities. Teams experiencing the same delivery failure often flag it before an official update goes up.

What Actually Breaks During an xMatters Outage

xMatters is a multi-service platform — what breaks depends on which piece fails.

Component	What it covers	Impact when down
Alert / Notification Delivery	Sends pages via SMS, voice, push, email	On-call engineers don't get paged for real incidents
On-Call Scheduling	Rotations, escalation policies	Wrong person (or no one) gets escalated to
Integrations / Webhooks	Connects monitoring tools (Datadog, PagerDuty-style triggers, etc.) to xMatters	Upstream alerts never reach xMatters to begin with
Admin Console	Manage schedules, escalation paths, users	Teams can't update on-call rotations or fix broken routing
API	Programmatic event creation and resolution	Automated incident creation/closing silently fails
Mobile App	Receiving and acknowledging pages on the go	Engineers see nothing on their phone even when a page technically "sent"

An alert delivery outage is the worst-case scenario here: it's not a feature being unavailable, it's the entire reason the tool exists failing silently, with no user-facing error to tip anyone off.

Common xMatters Failure Symptoms

What you see	What it usually means
On-call engineer never gets paged	Delivery service issue, or a carrier/SMS gateway problem on xMatters' side
Escalation skips the right person	On-call scheduling data issue, or a misconfigured escalation policy
Monitoring tool fires but xMatters never creates an incident	Integration/webhook ingestion failure
Mobile app shows no new alerts	Push notification delivery issue, separate from SMS/voice
Admin console won't save a schedule change	Admin backend degraded
API calls to create/resolve events fail or time out	API layer issue

Why xMatters Goes Down

Carrier and SMS/voice gateway issues. Page delivery depends on third-party telecom carriers. A carrier-side problem can degrade or delay SMS and voice paging even when xMatters' own systems are fully healthy.

Integration/webhook ingestion problems. If the upstream monitoring tool sending events into xMatters changes its payload format or hits a rate limit, events can silently fail to create incidents — looking exactly like an xMatters outage from the outside.

Scheduled maintenance and deployments. Like any SaaS platform, xMatters ships updates to its alerting and scheduling infrastructure. Deployments occasionally cause brief disruptions.

Traffic spikes during widespread incidents. When a major cloud provider or widely-used SaaS has an outage, many customers' monitoring tools fire simultaneously — creating a surge of inbound events that can strain any alerting platform's ingestion, including xMatters', right when everyone needs it most.

Upstream cloud dependencies. xMatters depends on underlying cloud infrastructure. An incident with an upstream provider can cascade into delivery delays even when xMatters' own code is healthy.

What To Do During an xMatters Outage

Immediately:

1. Check Statusfield and xMatters' own status page — confirm it's actually xMatters and not a downstream integration issue
2. Fall back to a manual paging channel (phone tree, Slack, direct call) for anything currently in progress — don't wait for the primary tool to recover
3. If integrations feed xMatters, check the sending tool's delivery logs to confirm whether the event ever left, or if it's stuck on xMatters' side
4. Communicate the outage to your on-call team directly, since the tool you'd normally use to do that may be the thing that's down

If a real incident happened during the outage window:

• Document what you know about the xMatters outage window alongside the incident timeline — this matters for your own postmortem and for any SLA/compliance conversation about response time
• Verify every escalation step manually once xMatters is back, rather than assuming a queued page eventually reached someone
• Contact xMatters support if the disruption extends past a brief blip — enterprise plans typically include defined support response times

After it resolves:

• Audit your escalation logs for any incident that fired during the outage window to confirm it was actually acknowledged
• Re-test paging end-to-end (a real test page, not just a status check) before trusting the system again
• Add Statusfield monitoring so your team has an independent signal the next time xMatters status changes — one that doesn't depend on xMatters itself to reach you

Monitoring xMatters Like an SRE Team

xMatters is your incident response layer. Treating it that way means monitoring it proactively, with a tool that isn't part of the same failure domain.

1. Set up independent status monitoring — Statusfield tracks xMatters status continuously and alerts your team the moment something changes, over a channel that doesn't depend on xMatters being healthy.
2. Periodically test end-to-end paging — don't assume delivery works; confirm it with a real test page on a schedule.
3. Watch your integration health separately — since a silent webhook failure looks identical to an xMatters outage, monitoring the upstream side helps you diagnose faster.
4. Keep a documented manual fallback — a phone tree or backup paging channel that doesn't route through xMatters at all.

How to Get Instant xMatters Outage Alerts

Most teams find out about an xMatters issue when an incident goes unanswered — which is exactly the failure mode you built xMatters to prevent in the first place. By then you're explaining a missed page after the fact instead of catching the root cause in real time.

Monitor xMatters on Statusfield and get alerted the moment status changes, through a channel that's independent of xMatters' own infrastructure. Your team knows in seconds instead of after a missed page.

Start monitoring xMatters →

---

Frequently Asked Questions

Is xMatters down right now?

Check the live status at statusfield.com/services/xmatters for real-time xMatters service status updated continuously.

Why didn't I get paged even though there was a real incident?

This is usually either an alert delivery issue on xMatters' side (SMS/voice carrier problem) or an integration/webhook failure where the upstream monitoring tool's event never reached xMatters at all. Check the sending tool's delivery logs first, then check Statusfield and xMatters' own status page to rule out a platform-side issue.

How do I know if xMatters is down if the tool I'd use to find out is the one that's down?

Use an independent status monitor like Statusfield, which tracks xMatters continuously and alerts over a channel that doesn't depend on xMatters' own infrastructure being healthy.

Can an xMatters outage affect incident response SLAs?

Yes, if a page fails to deliver during a real incident, your team's response time is affected even though the underlying system issue and the alerting failure are two separate problems. Documenting the xMatters outage window alongside your incident timeline is important for postmortems and any SLA review.

How do I get alerts when xMatters goes down?

Set up xMatters monitoring on Statusfield. You'll get instant notifications via email or webhooks the moment xMatters status changes, independent of xMatters' own systems.

What should I do if a monitoring tool fires but xMatters never creates an incident?

Check the delivery logs on the sending tool to confirm the event actually left. This is usually an integration or webhook ingestion issue rather than a full xMatters platform outage — verify with Statusfield and xMatters' own status page before assuming it's platform-wide.