xMatters Status Page

Oct 1, 2026 · resolved Oct 1

The issue has been addressed, and all services have been restored. Thank you for your patience while we addressed this matter.

Sep 21, 2026

All SMS traffic to the US and Canada is now being delivered through our secondary short code 66936. We are currently monitoring the situation to ensure the implementation is stable and that all services are restored.

Aug 26, 2026 · resolved Sep 1

ServiceNow has resolved this issue on Friday, August 28, 2026 with a maintenance patch. The problem was related to an issue in the ServiceNow patch identified in their article KB3147727 (https://support.servicenow.com/kb_view.do?sysparm_article=KB3147727)

Jul 1, 2026 · resolved Jul 1

**What happened?**  On July 1st, 2026, some customers reported an issue to xMatters Customer Support where they were encountering authentication errors when accessing the web user interface.  **Why did it happen?**  This issue occurred because a database cluster reached 100% resource utilization, causing database requests to time out. An exceptional traffic pattern exposed a set of slow-running queries, which significantly increased query latency on the cluster. As latency increased, there was resource starvation and further degradation of the cluster's responsiveness, resulting in timeouts.  **How did we respond?**  As soon as Customer Support confirmed the issue, they engaged the Engineering teams to investigate. As designed, the system had restored itself before Engineering could implement any mitigation or recovery actions, but the teams were still able to identify and isolate the root cause.  **What are we doing to prevent it from happening again?**  To prevent this issue from reoccurring, the Engineering Team designed, developed, and tested a fix. They deployed the fix in the morning of Wednesday, July 8th, 2026, and it has been successfully implemented for all instances.

May 1, 2026 · resolved May 1

**What happened?**  On May 1st, 2026, some customers reported an issue to xMatters Customer Support where attempting to send a message via the web user interface or viewing an alert on the Alerts report resulted in an error being displayed. The issue only affected the Reporting functions in the EMEA region; the system continued to accept signals, generate alerts, and send notifications across all regions.  **Why did it happen?**  The issue occurred when, during routine database maintenance, the database called a mismatched version of the library, resulting in an internal database error. The version mismatch within the cluster was traced to a prior database engine upgrade where a subset of replica nodes did not restart into the upgraded version. At no point was there any risk to data integrity.  **How did we respond?**  As soon as Customer Support confirmed the issue, they engaged the Engineering teams, who were able to identify the root cause and restore version consistency across all nodes. The teams validated stability and confirmed that all services were restored.  **What are we doing to prevent it from happening again?**  The Engineering Team has added explicit post-upgrade verification checks and monitoring to ensure node alignment is confirmed and maintained. This will provide safeguards to ensure node version alignment after upgrades and prevent this issue from reoccurring.

Is xMatters down right now?

No — xMatters is up. All systems operational as of Oct 12, 4:56 AM UTC.

What is xMatters's current status?

xMatters: All Systems Operational. Alert24 checks xMatters's status page continuously and can notify you the moment it changes.

How do I get alerted when xMatters goes down?

Alert24 monitors xMatters and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.