Xmatters の障害履歴

1. 2026年10月20日 6:24 UTCinvestigating

   xMatters モニタリングツールは、欧州地域にあるクライアントに対して xMatters On-Demand の潜在的な問題を特定しました。 現在、課題を調査し、情報として更新します。 特定のサービスに影響するインシデントの詳細をご覧ください。 問題が発生した場合、またはこの問題があなたのサービスに影響を及ぼすかどうかわからない場合は、https://support.xmatters.com/hc/en-us/requests/new で xMatters クライアントアシスタンスにお問い合わせください。当社のサポート担当者がサポートをお待ちしています.

2. 2026年10月20日 6:31 UTCidentified

   XMatters インシデントレスポンスチームは、問題のソースを特定し、修正に取り組んでいます。 ソリューションが特定され導入されたら更新します.

3. 2026年10月20日 6:36 UTCmonitoring

   XMatters Incident Response チームは、問題の修正を行いました。 現在、実装が安定していることを確認する状況を監視し、すべてのサービスが復元されていることを確認します.

4. 2026年10月20日 22:27 UTCresolved

   問題が解決され、すべてのサービスが復元されました。 誠に有難うございます.

5. 2026年10月24日 0:21 UTCpostmortem

   **何が起こったのか?** 2026年10月19日、xMatters内部監視ツールは10:03 PM Pacificでサービス劣化を検知しました。 直後、一部の顧客は、xMattersにアクセスしたり、統合および通知サービスを使用して問題が発生することを報告しました。 **なぜ起きたの?** Google Cloud は EU-West-2 地域に影響を及ぼす停電を経験しました。 影響を受けた地域におけるXMattersサービスの中断 **対応方法は?** xMatters サポート、エンジニアリング、およびオペレーションチームは、主要なインシデント管理プロセスを開始し、影響を受けるシステムが他の地域に及ぼす影響を緩和しました。 システム移行に伴いサービスが利用可能になりました。 xMatter は、Google がその影響を受けた地域での回復作業を続けながら、監視および検証サービスの安定性に残ります。 **これから起こらないことをやっているの?** xMatters は、インフラプロバイダーの停電の影響を緩和するために、地域の回復力で設計されています。 この事件では、被災したサービスを別の地域に移行する目的で運営する責任ある措置。 エンジニアリングとオペレーションは、インシデントの解決反応を見直し、回復手順を合理化し、同様のイベント中に回復時間を削減する機会を特定しています.

公式のインシデント更新を自動翻訳しています。

1. 2026年10月1日 17:22 UTCinvestigating

   xMatters モニタリングツールは、北米地域にあるクライアントに対して xMatters On-Demand の潜在的な問題を特定しました。 現在、課題を調査し、情報として更新します。 特定のサービスに影響するインシデントの詳細をご覧ください。 問題が発生した場合、またはこの問題があなたのサービスに影響を及ぼすかどうかわからない場合は、https://support.xmatters.com/hc/en-us/requests/new で xMatters クライアントアシスタンスにお問い合わせください。当社のサポート担当者がサポートをお待ちしています.

2. 2026年10月1日 17:30 UTCinvestigating

   今後もこの問題について調査を続けてまいります.

3. 2026年10月1日 17:40 UTCidentified

   XMatters インシデントレスポンスチームは、問題のソースを特定し、修正に取り組んでいます。 ソリューションが特定され導入されたら更新します.

4. 2026年10月1日 17:45 UTCmonitoring

   XMatters Incident Response チームは、問題の修正を行いました。 現在、実装が安定していることを確認する状況を監視し、すべてのサービスが復元されていることを確認します.

5. 2026年10月1日 18:56 UTCresolved

   問題が解決され、すべてのサービスが復元されました。 誠に有難うございます.

6. 2026年10月13日 20:12 UTCpostmortem

   **何が起こったのか?** 2026年10月1日、XMattersは、9:27 AM Pacificで初めて検出されたサービス劣化を監視し、最初の顧客レポートは午前10時03分に届きました。 US-EAST1の顧客は、統合がアラートや通知を開始したときに、断続的なWebインターフェイスアクセスの問題、APIのタイムアウト、および遅延または失敗を経験しました。 US-CENTRAL1のお客様の中には、同じ期間中に音声通知の問題が発生する場合があります。 **なぜ起きたの?** US-EAST1 の自動インフラスケーリング中に、複数のアプリケーションサービスが同じ計算リソースに集中できるようになりました。 そのリソースは、その処理能力に達しました, 顧客要求に対応するために利用可能な容量を減らす. 依存する xMatters 機能全体でサービス劣化が続くため、処理能力が追加されました。 **対応方法は?** 初めての顧客は、問題が報告された直後に、xMatters Customer Support は、内部の主要なインシデント管理プロセスを開始し、エンジニアリングおよびオペレーションチームに従事しました。 インシデントレスポンスチームは、サービス容量を増加させ、影響を受けたサービスを監視し、Webインターフェイス、API、統合、通知処理を横断したリカバリを検証しました。 本サービスは10時37分までに安定化し、第一次顧客への影響は10時46分に終了いたしました。 午前11時56分に公開事故を解決する前に、チームを継続的に監視します。 **これから起こらないことをやっているの?** エンジニアリングは、サービス容量とワークロードの配布制御を見直し、同じ計算リソースの複数の重要なサービスのリスクを削減します。 チームはまた、必要な容量が常に利用可能であることを確認するために、容量の問題が早期に識別されるように、サービス健康チェックと警戒を見直しています.

公式のインシデント更新を自動翻訳しています。

1. 2026年9月21日 18:14 UTCinvestigating

   xMatters は、米国とカナダのショートコード 87961 の数字に、すべての地域のクライアントの xMatters SMS 通知の問題を特定しました。 66936 秒の短いコードに失敗しました。 現在、課題を調査し、情報として更新します。 問題が発生した場合、またはこの問題があなたのサービスに影響を及ぼすかどうかわからない場合は、https://support.xmatters.com/hc/en-us/requests/new で xMatters クライアントアシスタンスにお問い合わせください。当社のサポート担当者がサポートをお待ちしています.

2. 2026年9月21日 18:41 UTCmonitoring

   米国とカナダへのすべてのSMSトラフィックは、当社の二次ショートコード66936を介して配信されています。 現在、実装が安定していることを確認する状況を監視し、すべてのサービスが復元されていることを確認します.

3. 2026年10月16日 16:03 UTCresolved

   ショートコードの問題は、カナダと米国へのすべてのSMS通知が87961ショートコードから配信されました。 誠に有難うございます.

4. 2026年10月16日 16:24 UTCpostmortem

   **何が起こったのか?** 2026年9月21日には、北米のエンドユーザーにSMSメッセージが送信できなかったXMatters Client Assistanceの問題が報告されました。 **なぜ起きたの?** SMSメッセージ送信に使用されるショートコードが利用できなくなったため、SMS配信障害が発生しました。 システムは、二次メッセージングプロバイダを介して自動的に失敗したメッセージをルーティングする必要があります。 しかし、これらの失敗のために返された特定のエラーは、設定された障害プロセスをトリガーしなかった、米国とカナダのエンドユーザーに破壊されたSMS配信を引き起こしました。 **対応方法は?** エンジニアリングがSMS配信の問題を特定したら、主要なインシデント管理プロセスを開始し、メッセージング構成から影響を受けるショートコードを削除し始めました。 このプロセス中に、エンジニアリングは、システムが自動的にSMSトラフィックをセカンダリメッセージングプロバイダに切り替えることを防ぐ追加の問題に遭遇しました。 手動で2次プロバイダへのスイッチを完了し、SMS配達を元通りにするために介入しました。 サービスが回復した後、エンジニアリングは、SMS配信が正常に動作していることを確認するためにシステムを監視しました。 **これから起こらないことをやっているの?** エンジニアリングは、以前の主要なショートコードを復元するために働いた間、二次メッセージングプロバイダを介してSMSトラフィックをルーティングしました。 エンジニアリングは、この特定のエラーが発生したときに、システムが自動的にプロバイダーを切り替えるのを防ぐフェイルオーバー動作にも対処しています。 プロセスへのこれらの改善は、将来のSMS配信を破壊する同様のショートコードの問題のリスクを減らすでしょう.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月1日 19:53 UTCinvestigating

   xMatters の監視ツールは、北米地域にあるクライアントに対して xMatters On-Demand の問題を 1 つのデータベースクラスターに限って特定しました。 現在、課題を調査し、情報として更新します。 問題が発生した場合、またはこの問題があなたのサービスに影響を及ぼすかどうかわからない場合は、https://support.xmatters.com/hc/en-us/requests/new で xMatters クライアントアシスタンスにお問い合わせください。当社のサポート担当者がサポートをお待ちしています.

2. 2026年7月1日 20:07 UTCmonitoring

   XMatters Incident Response チームは、問題の修正を行いました。 現在、実装が安定していることを確認する状況を監視し、すべてのサービスが復元されていることを確認します.

3. 2026年7月1日 20:21 UTCresolved

   問題が解決され、すべてのサービスが復元されました。 誠に有難うございます.

4. 2026年7月9日 19:21 UTCpostmortem

   **何が起こったのか?** 2026年7月1日、一部の顧客は、Webユーザーインターフェイスにアクセスしたときに認証エラーに遭遇したxMattersカスタマーサポートに問題が報告されました。 **なぜ起きたの?** データベースクラスターが100%のリソース使用率に達したため、この問題が発生し、データベースのリクエストがタイムアウトされるようにしました。 例外的なトラフィックパターンは、クラスターのクエリレイテンシを大幅に増加させるスローランニングクエリのセットを露出しました。 レイテンシが増加するにつれて、クラスターの応答性のリソースの飢餓とさらなる劣化が起こり、タイムアウトをもたらします。 **対応方法は?** カスタマーサポートが問題が確認できたらすぐに、エンジニアリングチームに調査を実施しました。 設計されているように、エンジニアリングが緩和または回復アクションを実行できる前にシステム自体を復元しましたが、チームは依然として根本的な原因を特定し、隔離することができます。 **これから起こらないことをやっているの?** この問題が再発を防ぐため、エンジニアリングチームは設計、開発、修正を行いました。 朝、7月8日(水)、2026(水)に固定を配備し、全インスタンスで正常に実装されています.

公式のインシデント更新を自動翻訳しています。

1. 2026年5月1日 8:45 UTCinvestigating

   xMatters have identified a potential issue with the xMatters Web User Interface for some clients located in the Europe region. Accessing some pages including Alert details produces an error. We are currently investigating the issue and will update as information becomes available. If you are also experiencing issues, or if you're not sure whether this issue impacts your service, please contact xMatters Client Assistance at https://support.xmatters.com/hc/en-us/requests/new - our support agents are waiting to help.

2. 2026年5月1日 9:01 UTCidentified

   The xMatters Incident Response team has identified the source of the issue and is working on a fix. We will update once a solution has been identified and implemented.

3. 2026年5月1日 9:03 UTCmonitoring

   The xMatters Incident Response team has deployed a fix for the issue. We are currently monitoring the situation to ensure the implementation is stable and that all services are restored.

4. 2026年5月1日 9:19 UTCresolved

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

5. 2026年5月12日 20:32 UTCpostmortem

   **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.

1. 2026年4月1日 14:06 UTCinvestigating

   xMatters monitoring tools have identified a potential issue with the API for some clients located in the North America region. We are currently investigating the issue and will update as information becomes available. If you are also experiencing issues, or if you're not sure whether this issue impacts your service, please contact xMatters Client Assistance at https://support.xmatters.com/hc/en-us/requests/new - our support agents are waiting to help.

2. 2026年4月1日 14:30 UTCidentified

   The xMatters Incident Response team has identified an issue with the API for some clients located in the North America region which is causing some intermittent API timeouts. This is also causing issues with running reports in the system. We are currently investigating the issue and will update as information becomes available.

3. 2026年4月1日 14:33 UTCmonitoring

   The xMatters Incident Response team has deployed a fix for the issue. We are currently monitoring the situation to ensure the implementation is stable and that all services are restored.

4. 2026年4月1日 14:36 UTCresolved

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

5. 2026年4月6日 23:21 UTCpostmortem

   **What happened?**  On April 1st, 2026, some customers reported an issue to xMatters Customer Support where the Alerts or Notifications reports were timing out and failing to load.  **Why did it happen?**  This issue occurred because a backend service was experiencing significant unexpected load that caused report processing to be delayed. The ongoing resource constraint resulted in timeouts.  **How did we respond?**  As soon as customers reported an issue, Customer Support launched an investigation and escalated to the Engineering teams. The teams initiated rolling restart procedures for the applicable backend services to restore functionality. Once the rolling restart was completed, service was fully restored.  **What are we doing to prevent it from happening again?**  The Engineering teams are currently working to identify any possible bottlenecks that may have caused performance issues. In the interim, they have increased and adjusted resource allocation for several services to handle potential processing delays and prevent potential recurrences.

1. 2026年3月10日 20:36 UTCinvestigating

   We have reports that some users are not able to login to xMatters using SSO to login to the xMatters Web User Interface in All Regions. We are currently investigating the issue and will update as information becomes available. Native Login still works to bypass SSO. If you are also experiencing issues, or if you're not sure whether this issue impacts your service, please contact xMatters Client Assistance at https://support.xmatters.com/hc/en-us/requests/new - our support agents are waiting to help.

2. 2026年3月10日 20:51 UTCidentified

   The xMatters Incident Response team believes they have identified the source of the issue and is working on a fix. We will update once a solution has been identified and implemented.

3. 2026年3月10日 20:54 UTCresolved

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

4. 2026年3月20日 18:01 UTCpostmortem

   **What happened?**  On March 10th, 2026, some customers reported an issue to xMatters Customer Support where they were encountering a 404 error page when attempting to log in to their instances via SSO. Some users may also have encountered a “We’ve run into a problem while retrieving your data.” error message.  **Why did it happen?**  This issue occurred during a routine maintenance update to the xMatters platform. Although several components of the platform were updated, specific configurations of the component related to SSO-based authentication conflicted with the update and resulted in 404 errors. This issue was limited to those few customers that had specific criteria set for their SSO configuration.  **How did we respond?**  As soon as customers reported the issue, Customer Support verified the issue and escalated immediately to Engineering. The team traced the issue to the maintenance deployment and initiated rollback procedures to restore functionality. Once the rollback was completed, the 404 errors ceased and service was confirmed restored.  **What are we doing to prevent it from happening again?**  The Engineering teams have implemented additional testing for any configuration criteria related to the SSO-based authentication component. In addition, they have begun working on an improved maintenance plan to prevent further issues that could occur during similar deployments.

1. 2025年11月21日 13:54 UTCinvestigating

   xMatters monitoring tools have identified a potential issue with xMatters On-Demand for some clients located in the North America region. This is affecting users located near the Asia Pacific Region attempting to access xMatters. We are currently investigating the issue and will update as information becomes available. Please see incident details for specific services impacted. If you are also experiencing issues, or if you're not sure whether this issue impacts your service, please contact xMatters Client Assistance at https://support.xmatters.com/hc/en-us/requests/new - our support agents are waiting to help.

2. 2025年11月21日 13:55 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025年11月21日 14:01 UTCresolved

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

4. 2025年11月27日 18:42 UTCpostmortem

   **What happened?** On November 21, 2025, at 12:50 PM UTC, the xMatters internal monitoring tools detected irregular behavior in how internal traffic was being routed. Some customers in the APAC region communicating with services in North America \(specifically US-East\) may have encountered intermittent request failures or increased latency. Only traffic between these two regions was affected; all other systems and regions continued normal operations. **Why did it happen?** A temporary network disruption between Australia Southeast and US-East caused one internal routing node in Australia to lose accurate information about available backend systems in USEast. The node generated an incomplete routing configuration and temporarily stopped directing traffic to US-East. Under normal circumstances, routing updates refresh automatically when connectivity returns. In this case, the affected node did not recover cleanly and remained in a stale state until Engineering intervened. **How did we respond?** As soon as Engineering was alerted through internal monitoring, they engaged with the platform engineering team, service owners and Customer Support to launch an investigation. The teams reached out to impacted customers to validate issue symptoms and restarted routing components in both affected regions to force a configuration refresh. Once the restart completed, routing returned to normal levels while the teams continued to monitor and investigate the root cause. They were able to confirm that only one routing node and specific cross-region traffic was impacted. **What are we doing to prevent it from happening again?** While teams were mitigating this issue, they created new alerting rules to detect the routing patterns they observed during the incident and expanded internal monitoring to help identify when routing nodes fail to refresh their configuration or otherwise enter a ‘stale’ state. The teams also have planned and prepared infrastructure updates that will further reduce the risk of similar issues. These include improved configuration recovery behavior, enhanced stability for routing components, and additional logging and observability improvements for diagnosing routing anomalies. They will deploy these updates once the current code freeze window has elapsed.

1. 2025年10月20日 10:20 UTCidentified

   xMatters monitoring tools have identified a issue with xMatters Conferencing and Voice calls for clients in All Regions. The issue is due to downstream provider outages.

2. 2025年10月20日 12:23 UTCmonitoring

   Our downstream providers have deployed a fix and testing shows conferencing and voice systems are now working as expected. We are currently monitoring the situation to ensure the implementation is stable and that all services are restored.

3. 2025年10月21日 16:34 UTCresolved

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

4. 2025年10月29日 21:52 UTCpostmortem

   **What happened?**  On October 20th, 2025, at approximately 1:21 AM Pacific, customers began reporting an issue affecting live call routing, conferences, and voice notifications. During this issue, customers in all regions would have been affected. **Why did it happen?**  This issue was caused by a global AWS outage that impacted one of our downstream providers, resulting in voice notifications, live call routing, and conferencing they were handling to fail.  **How did we respond?**  As soon as the first customer reported an issue, Customer Support engaged the Engineering teams and launched an investigation. Once they identified the root cause, the teams updated the primary provider for affected regions to an alternate provider that was not affected by the AWS outage. When the new provider was assigned, customers reported that all services were operating correctly.  **What are we doing to prevent it from happening again?**  While this issue was out of our control or that of our provider, we are working to identify potential ways to improve resilience in case of external factors such as this.

1. 2025年10月10日 22:58 UTCmonitoring

   The xMatters monitoring tools have alerted Customer Support to a potential issue with the integration platform in the North America region. Our technical teams have identified intermittent request failures and occasional slowdowns, though the service appears to be responsive and recovering correctly. We are continuing to monitor the situation and mitigating where possible, though some users may encounter a 5xx response code when submitting a request. If you are also experiencing issues, or if you're not sure whether this issue impacts your service, please contact xMatters Client Assistance at https://support.xmatters.com/hc/en-us/requests/new - our support agents are waiting to help.

2. 2025年10月14日 15:58 UTCresolved

   The issue has been addressed, and all services are running as expected. Thank you for your patience while we addressed this matter.

3. 2025年10月31日 18:48 UTCpostmortem

   **What happened?**  On October 10th, 2025, at approximately 4:14 PM Pacific, the xMatters internal monitoring tools alerted Customer Support to service degradation related to an issue that was already being internally monitored with the Integration Platform in the North American region. While this issue was being investigated and mitigated, customers may have experienced intermittent request failures and occasional slowdowns.  **Why did it happen?**  These particular issues were caused by a security update that caused conflicts with the underlying runtime environment, specifically the memory management routine. Slow performance of the routine was triggering frequent health checks for a request processing service and causing automatic restarts.  **How did we respond?**  As soon as the internal monitoring tools alerted Engineering to a potential issue, they began performing manual rolling restarts and deployed more forgiving liveness checks to avoid increasing error rates and to minimize any potential impact to customers. They also increased resources for the impacted service to improve responsiveness of the underlying routine and deployed a configuration fix to the Http Client Cache to try and stabilize the system. While mitigating the potential impact, they also increased monitoring levels as they continued to investigate the root cause and were able to deploy an update to the service and environment configuration on October 13 that resolved the issue. They continued monitoring and confirmed that the system was stable and all services were operational.  **What are we doing to prevent it from happening again?**  Engineering has updated the backend service and deployed additional updates and monitoring to the system configuration that will improve overall stability for the environment and prevent this issue from reoccurring.

1. 2025年9月24日 3:59 UTCinvestigating

   xMatters identified a issue with the Apple iOS Push Notifications for clients in All Regions. We are currently investigating the issue and will update as information becomes available. If you are also experiencing issues, or if you're not sure whether this issue impacts your service, please contact xMatters Client Assistance at https://support.xmatters.com/hc/en-us/requests/new - our support agents are waiting to help.

2. 2025年9月24日 4:19 UTCidentified

   xMatters has identified the issue with the Apple Push notifications for clients located in the in All Regions. We are currently investigating a solution and will update as information becomes available. If you are also experiencing issues, or if you're not sure whether this issue impacts your service, please contact xMatters Client Assistance at https://support.xmatters.com/hc/en-us/requests/new - our support agents are waiting to help.

3. 2025年9月24日 4:32 UTCidentified

   We are continuing to work on a fix for this issue.

4. 2025年9月24日 4:34 UTCinvestigating

   xMatters has identified the issue with the Apple Push notifications for clients located in the in All Regions. We are currently deploying a solution and will update as information becomes available. Asia Pacific customers can now receive Apple push notifications.

5. 2025年9月24日 4:43 UTCresolved

   The issue has been addressed, and Apple Push notifications have been restored in all regions. Thank you for your patience while we addressed this matter.

6. 2025年10月15日 6:16 UTCpostmortem

   **What happened?**  On September 23rd, 2025, at approximately 8:31 PM Pacific, the xMatters internal monitoring tools alerted the xMatters Support Team to an issue with Apple iOS notifications. Users were not receiving notifications on Apple iOS devices; other device types and alert and response processing were not impacted and continued to operate without interruption.  **Why did it happen?**  The issue occurred because of a backend service patch applied by the Engineering teams that affected necessary dependencies for Apple Push notification delivery.  **How did we respond?**  As soon as the monitoring tools alerted the Support team, they engaged the Engineering teams to launch an investigation. The teams quickly identified the source of the issue as a recent backend service patch and initiated a rollback of the patch. Once the rollback was complete, the teams confirmed that all services had been restored.  **What are we doing to prevent it from happening again?**  The Engineering team is working to enhance testing of future patches and improving visibility into the health of services. This will help to proactively resolve issues or, when necessary, initiate rollbacks more quickly without impacting customers.

1. 2025年8月6日 3:27 UTCinvestigating

   xMatters monitoring tools have identified a potential issue with xMatters On-Demand for clients in North America that are hosted in the on us-central1 region. We are currently investigating the issue and will update as information becomes available. Please see incident details for specific services impacted. If you are also experiencing issues, or if you're not sure whether this issue impacts your service, please contact xMatters Client Assistance at https://support.xmatters.com/hc/en-us/requests/new - our support team is waiting to help.

2. 2025年8月6日 3:44 UTCidentified

   The xMatters Incident Response team has identified an issue with our message routing system and is working on a fix. We will update once a solution has been identified and implemented.

3. 2025年8月6日 3:59 UTCmonitoring

   The xMatters Incident Response team has deployed a fix for the issue. We are currently monitoring the situation to ensure the implementation is stable and that all services are restored.

4. 2025年8月6日 5:18 UTCresolved

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

5. 2025年8月14日 1:16 UTCpostmortem

   ### What happened? On August 5th, 2025, at approximately 7:53 PM Pacific, the xMatters internal monitoring tools alerted the xMatters Support team to an issue in the North America region with notification delivery. Some xMatters customers may have experienced delays when receiving notifications or noticed failed alerts in the system. ### Why did it happen? The issue occurred because of a network problem that disrupted communication between parts of the queuing system. This caused some components to become temporarily out of sync, leading to timeouts, internal connectivity failures, and a small number of messages not being processed during the disruption. As the system recovered, some performance was degraded until normal operation could be restored. ### How did we respond? As soon as the xMatters monitoring tools reported an issue, the xMatters Support Team initiated the internal Major Incident Management process and engaged the Engineering and incident response teams. The teams quickly mitigated the issue and restored performance by redirecting traffic from our message queuing system in the affected region \(us-central\) to our message queuing system in another local region \(us-east\). After the issue was resolved, the teams directed traffic back to the restored region. ### What are we doing to prevent it from happening again? The Engineering team has determined that the best approach to prevent this issue from reoccurring is to replace the current message queuing system. Work on the replacement system is well underway and the teams will retire the current system as soon as they have finished the replacement.

1. 2025年6月23日 20:14 UTCinvestigating

   We have identified a problem affecting the xMatters Support Center. Our team is investigating and working to resolve the issue. Details: Users will be unable to access the xMatters Support Center. Tickets can be created via email or through Support line.

2. 2025年6月23日 20:46 UTCresolved

   We have now resolved the issue with our support center.

1. 2025年6月12日 18:47 UTCinvestigating

   xMatters monitoring tools have identified a potential issue with the xMatters Integration Platform for some clients located in the North America region. We are currently investigating the issue and will update as information becomes available. If you are also experiencing issues, or if you're not sure whether this issue impacts your service, please contact xMatters Client Assistance at https://support.xmatters.com/hc/en-us/requests/new - our support agents are waiting to help.

2. 2025年6月12日 19:04 UTCidentified

   The xMatters Incident Response team has identified the source of the issue with an upstream provider and is working with them on identifying a fix. We will update once a solution has been identified and implemented.

3. 2025年6月12日 19:34 UTCidentified

   We are still working with our upstream providers. Their engineers are continuing to mitigate the issue and we have confirmation that the issue is recovered in some locations. We do not have an ETA on full mitigation at this point. We continue to operate in a degraded state.

4. 2025年6月12日 20:06 UTCidentified

   We are continuing to work with our upstream providers. Their engineers have confirmed that the underlying dependency is recovered in most regions and all their engineering teams are actively engaged and working on service recovery. We do not have an ETA for full service recovery.

5. 2025年6月12日 20:53 UTCmonitoring

   At this time, we are seeing all services recovering. We will continue to monitor until we have confirmation from our upstream provider that they have fully resolved the issue.

6. 2025年6月12日 22:12 UTCresolved

   We are currently seeing error rates down to normal levels and we are considering this issue resolved at this time

7. 2025年6月23日 17:40 UTCpostmortem

   **What happened?**  On June 12th, 2025, at approximately 11:29 AM Pacific, the xMatters internal monitoring tools alerted to an issue in the North America region with the xMatters integration platform. While the issue was in progress, some xMatters customers may have experienced workflows not executing correctly or signals not being accepted as expected.  **Why did it happen?**  The issue occurred because multiple Google Cloud and Google Workspace products experienced external API issues for about three hours between the hours of 10:49 AM to 1:49 PM Pacific.  **How did we respond?**  As soon as the xMatters monitoring tools reported an issue with the xMatters integration platform, the xMatters Customer Support team initiated the internal Major Incident Management process and engaged the Engineering and incident response teams. The teams quickly determined that the issues were due to problems with an upstream provider and immediately opened a support case for them to investigate. They continued to work with the provider throughout the incident and confirmed with their engineers as they recovered the underlying dependencies.  **What are we doing to prevent it from happening again?**  The xMatters Support and Engineering teams requested an RCA and prevention methods from the upstream provider. In their response, they confirmed that they will be modularizing their Service Control architecture to prevent failures from affecting the entire service.

1. 2025年5月13日 17:45 UTCinvestigating

   xMatters monitoring tools have identified a potential issue with xMatters On-Demand for some clients located in the Europe region. We are currently investigating the issue and will update as information becomes available. Please see incident details for specific services impacted. If you are also experiencing issues, or if you're not sure whether this issue impacts your service, please contact xMatters Client Assistance at https://support.xmatters.com/hc/en-us/requests/new - our support agents are waiting to help.

2. 2025年5月13日 17:53 UTCidentified

   The xMatters Incident Response team has identified the source of the issue and is working on a fix. We will update once a solution has been identified and implemented.

3. 2025年5月13日 17:54 UTCidentified

   We are continuing to work on a fix for this issue.

4. 2025年5月13日 18:03 UTCmonitoring

   The xMatters Incident Response team has deployed a fix for the issue. We are currently monitoring the situation to ensure the implementation is stable and that all services are restored.

5. 2025年5月13日 20:46 UTCresolved

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

6. 2025年5月27日 20:50 UTCpostmortem

   **What happened?**  On May 13, 2025 at approximately 10:45 AM Pacific, xMatters internal monitoring tools identified an issue where customers in the EU region experienced intermittent web UI and API timeouts.  **Why did it happen?**  The issue occurred because a backend queueing service experienced network timeouts during an unpredictable rapid increase in usage. The increase in resource consumption due to the surge in network usage caused service timeouts and restarts, as well as higher latency which caused further delays in responses to backend requests.  **How did we respond?**  xMatters internal monitoring tools alerted the xMatters Incident Response Team to the issue, then the team launched the internal SEV-1 process. Due to early detection, Engineering teams were able to scale up the queueing services to prevent further service degradation and availability issues. The network timeouts were resolved after resources were scaled up to accommodate the increase in usage.  **What are we doing to prevent it from happening again?**  The Engineering teams have adjusted resources to better compensate for sudden usage increases and to prevent them from affecting backend services. The improvement in resource allocation and adaptability should prevent similar issues from occurring in the future.

1. 2025年4月3日 17:15 UTCinvestigating

   xMatters monitoring tools have identified a potential issue with xMatters Integration Platform for some clients in All Regions. We are currently investigating the issue and will update as information becomes available. If you are also experiencing issues, or if you're not sure whether this issue impacts your service, please contact xMatters Client Assistance at https://support.xmatters.com/hc/en-us/requests/new - our support agents are waiting to help.

2. 2025年4月3日 18:28 UTCidentified

   The xMatters Incident Response team has identified the source of the issue and is still working on a fix. We will update once a solution has been identified and implemented.

3. 2025年4月3日 18:44 UTCidentified

   The xMatters Incident Response team has identified the source of the issue and is actively working on a fix, there is no current estimate on resolution time. We will update once a solution has been implemented.

4. 2025年4月3日 20:26 UTCidentified

   The xMatters Incident Response team has identified the source of the issue and is still actively working on a fix, there is no current estimate on resolution time. We will update once a solution has been implemented.

5. 2025年4月3日 21:00 UTCidentified

   The xMatters Incident Response team has identified the source of the issue and is working on a fix. We will update once a solution has been identified and implemented.

6. 2025年4月3日 21:13 UTCidentified

   The xMatters Incident Response team has identified the source of the issue and are currently testing a fix. We will provide another update shortly.

7. 2025年4月3日 21:18 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

8. 2025年4月3日 21:45 UTCresolved

   This incident has been resolved.

9. 2025年4月7日 18:55 UTCpostmortem

   **What happened?** On April 3, 2025, at approximately 9:32 AM Pacific, the xMatters internal monitoring systems identified an issue where the system was not processing events initiated via Flow Designer across multiple regions. Customers may have observed the system not processing events or creating alerts while the issue was in progress. **Why did it happen?** The issue occurred when a routine update to add new permissions to the xMatters' Google Cloud Platform \(GCP\) unexpectedly removed required permissions. When the teams performed the update, which should not have had any impact to customers, the policy used in the automation script was the authoritative resource at the GCP project level rather than authoritative at the individual resource level. Although the teams tested the change before deploying it and found no changes beyond what was included in the update, when the update was deployed to production GCP removed all permissions that were not in the policy in the background. Because the policy only included the new permissions, all other permissions were removed. **How did we respond?** As soon as the xMatters monitoring tools reported an issue with the system not processing events, the incident response teams initiated the internal Major Incident Management process and engaged the Engineering and Support teams. The teams were able to quickly identify the recent update as the root cause of the issue and reverted the change to restore the permissions that were managed by the automation process. This restored access and functionality for most of the xMatters services, but restoring permissions for Flow Designer proved to be more complicated. The teams determined that missing permissions for the xMatters infrastructure were Google-generated permissions essential for specific xMatters services and engaged GCP Support to aid in the investigation. The teams generated a list of all permissions that existed prior to the update and designed a fix to re-apply them to the development environment. Once the teams had implemented the change and validated that the missing permissions and all services had been restored in the development environment, they moved to quickly apply the fix across all staging and production environments. Monitoring tools and customers confirmed that services were fully functional, and the teams continued to monitor the system as it processed all messages queued by the Flow Designer services. The system was fully restored at 2:46 PM Pacific. **What are we doing to prevent it from happening again?** The Engineering teams were able to identify all of the permissions created in the xMatters environment, including those that are created by Google, and are ensuring they are added to the management scripts. The teams are adding additional rigor to the application of these types of infrastructure changes to run idempotence tests after the changes are applied to ensure that there are no changes pending. Should a change be applied that fails this test, it will cause failures in development environments, which would catch and prevent a similar issue from occurring.

1. 2024年7月5日 16:19 UTCinvestigating

   xMatters monitoring tools have identified a potential issue with xMatters On-Demand for some clients located in the North America region. We are currently investigating the issue and will update as information becomes available. Please see incident details for specific services impacted. If you are also experiencing issues, or if you're not sure whether this issue impacts your service, please contact xMatters Client Assistance at https://support.xmatters.com/hc/en-us/requests/new - our support agents are waiting to help.

2. 2024年7月5日 16:36 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2024年7月5日 17:16 UTCresolved

   This incident has been resolved.

4. 2024年7月12日 20:07 UTCpostmortem

   **What happened?** On July 5th, at approximately 8:35AM Pacific, the xMatters monitoring tools alerted Customer Support to an issue where alert notifications were not being sent out for some customers in the North America region. Some customers attempting to initiate alerts may have encountered long delays in processing or may have had requests time out. **Why did it happen?** This issue occurred due to a sudden spike in the number of resources required by our backend services. The resulting memory overload issue caused some request handlers to time out before they could properly process incoming alerts. **How did we respond?** As soon as the xMatters Customer Support team confirmed the issue from the monitoring tools, they initiate the internal major incident management process and engaged the xMatters Engineering teams. To immediately mitigate the issue and restore service quickly, the incident response teams performed a rolling restart for the affected services. As soon as the restart was completed, the system resumed processing alerts and all services were restored. **What are we doing to prevent it from happening again?** The Engineering teams have implemented a performance enhancement for backend service queries. In addition, the teams are evaluating and testing additional methods to help mitigate resource spikes and prevent them from impacting alert notifications in the future. Once development and testing are complete, we'll deploy these changes with our regularly scheduled maintenance. **Timeline:** July 5th, 2024 8:35AM PT - xMatters internal monitoring tools alert to potential issue. 9:22AM PT - Issue identified. 9:36AM PT - Rolling restart initiated. 10:16AM PT - Issue Resolved.

1. 2024年7月1日 6:23 UTCinvestigating

   xMatters monitoring tools have identified a potential issue with xMatters for some clients in the North America region. We are currently investigating the issue and will update as information becomes available. If you are also experiencing issues, or if you're not sure whether this issue impacts your service, please contact xMatters Client Assistance at https://support.xmatters.com/hc/en-us/requests/new - our support agents are waiting to help.

2. 2024年7月1日 6:39 UTCmonitoring

   The xMatters Incident Response team has deployed a fix for the issue. We are currently monitoring the situation to ensure the implementation is stable and that all services are restored.

3. 2024年7月1日 8:21 UTCresolved

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

1. 2024年6月18日 23:16 UTCinvestigating

   xMatters monitoring tools have identified a potential issue with xMatters for some clients in the North America region. We are currently investigating the issue and will update as information becomes available. If you are also experiencing issues, or if you're not sure whether this issue impacts your service, please contact xMatters Client Assistance at https://support.xmatters.com/hc/en-us/requests/new - our support agents are waiting to help.

2. 2024年6月18日 23:26 UTCidentified

   The xMatters Incident Response team has identified the source of the issue and is working on a fix. We will update once a solution has been identified and implemented.

3. 2024年6月18日 23:34 UTCmonitoring

   The xMatters Incident Response team has deployed a fix for the issue. We are currently monitoring the situation to ensure the implementation is stable and that all services are restored.

4. 2024年6月18日 23:38 UTCresolved

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

1. 2024年5月24日 1:00 UTCinvestigating

   We are currently investigating an issue with one of our scheduler services impacting customers in Australia.

2. 2024年5月24日 1:03 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024年5月24日 1:04 UTCinvestigating

   xMatters monitoring tools have identified a potential issue with xMatters On-Demand for some clients located in the Asia Pacific region. We are currently investigating the issue and will update as information becomes available. Please see incident details for specific services impacted. If you are also experiencing issues, or if you're not sure whether this issue impacts your service, please contact xMatters Client Assistance at https://support.xmatters.com/hc/en-us/requests/new - our support agents are waiting to help.

4. 2024年5月24日 1:08 UTCidentified

   The xMatters Incident Response team has identified the source of the issue and is working on a fix. We will update once a solution has been identified and implemented.

5. 2024年5月24日 1:12 UTCmonitoring

   The xMatters Incident Response team has deployed a fix for the issue. We are currently monitoring the situation to ensure the implementation is stable and that all services are restored.

6. 2024年5月24日 1:23 UTCresolved

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