SAP Concur Outage History

Started Aug 19, 2025, 04:38 PM UTC· resolved Aug 19, 2025, 05:51 PM UTC

1. resolved Aug 19, 2025, 05:01 PM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Aug 19, 2025, 05:31 PM UTC

   In the China Data Center, logins through the SAP Concur website and SAP Concur mobile app is unavailable. Affected users may experience an error "This site can't be reached". when logging in. The Incident Response Team (IRT) is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.

3. resolved Aug 19, 2025, 05:58 PM UTC

   In the China Data Center, logins through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have experienced an error "This site can't be reached". when trying to logging in. Services have returned to normal operating levels. We will continue monitoring performance for the next 30 minutes to verify stability. Once verified as stable, the incident will be resolved.

4. resolved Aug 19, 2025, 06:16 PM UTC

   In the China Data Center, logins through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have experienced an error "This site can't be reached". when logging in. The services automatically self-recovered as the Incident Response Team (IRT) was investigating. We have verified that service performance is stable and will now resolve the incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete

5. resolved Sep 04, 2025, 08:02 AM UTC

   Impact as Reported: In the China Data Center, logins through the SAP Concur website and SAP Concur mobile app were unavailable. Affected users may have experienced an error "This site can't be reached". when trying to logging in. Root cause: Due to a problem at the internet service providers serving it, the China Data Center experienced connectivity issues between China and other geographical regions. While this initially only impacted users trying to access the Chinese Concur instance from outside the PRC, as the network issue persisted an application supporting the authentication process, that relies on a global service, started experiencing failures not being able to connect to it to renew expiring tokens, leading to the incident to impact users within the PRC as well. Once the connectivity was restored by the Chinese internet service providers, the authentication service was able to connect and access was restored for all users. Corrective Actions: Connectivity was restored on the internet service providers side, externally to to SAP Concur. A preventive action as been identified to add a local fallback mechanism to the global service used by the authentication workflow for when a region is unable to connect to other regions.

Read the full incident report →

Started Jun 30, 2025, 11:51 PM UTC· resolved Jul 01, 2025, 01:54 AM UTC

1. resolved Jul 01, 2025, 01:57 AM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Jul 01, 2025, 02:19 AM UTC

   In the US2 Data Center, creating JPT Route Search entries and entries made by Network IC card through the SAP Concur website and SAP Concur mobile app is below expected level. Affected users may encounter an error when attempting to select a route using the JPT expense type. The Incident Response Team (IRT) is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.

3. resolved Jul 01, 2025, 02:57 AM UTC

   In the US2 Data Center, creating JPT Route Search entries and adding entries made by Network IC card through the SAP Concur website and SAP Concur mobile app were below expected level. Affected users may have encountered an error when attempting to select a route using the JPT expense type. Additionally, approvers and processors were unable to view or verify the registered route information. Services have returned to normal operating levels. We will continue monitoring performance for the next 30-45 minutes to verify stability. Once verified as stable, the incident will be resolved.

4. resolved Jul 01, 2025, 03:42 AM UTC

   In the US2 Data Center, creating JPT Route Search entries and adding entries made by Network IC card through the SAP Concur website and SAP Concur mobile app were below expected level. Affected users may have encountered an error when attempting to select a route using the JPT expense type. Additionally, approvers and processors were unable to view or verify the registered route information. While the Incident Response Team (IRT) was actively investigating the issue, we observed that the affected service began to recover without manual intervention. We have verified that service performance is stable and will now resolve this incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report will be provided when that investigation is complete.

5. resolved Jul 22, 2025, 01:15 PM UTC

   Impact as Reported: In the US2 Data Center, logins through the SAP Concur website and SAP Concur mobile app were below expected levels. Affected users may have experienced an error, "Sorry something went wrong" when attempting to login. Root cause: An unforeseen increase in requests data volume for a Concur core config service, resulted in its caching layer exhausting network capacity, leading to high latency and/or request failures also affecting several downstream services involved in the authentication workflow and Next Gen Travel search/booking process. What caused this critical increase in requests data volume is still being investigated, more info will be provided as it becomes available. Corrective Actions Monitoring and alerting has been enhanced to provide visibility into network bandwidth utilization metrics for the various micro-services caching layer. The caching infrastructure is undergoing a sharding process to strongly mitigate the blast radius of similar incidents in the future. Additional action items are likely to result from the investigation that is still in progress.

6. resolved Jul 24, 2025, 11:07 AM UTC

   Impact as Reported: In the US2 Data Center, creating JPT Route Search entries and adding entries made by Network IC card through the SAP Concur website and SAP Concur mobile app were below expected level. Affected users may have encountered an error when attempting to select a route using the JPT expense type. Additionally, approvers and processors were unable to view or verify the registered route information. Root cause: The incident was triggered by a sudden increase of load on a database induced by a customer initiated large batch processing job. Impact on the database itself was aggravated to the point of rendering the database almost unresponsive by poorly optimized queries that have now been identified; additionally, a circuit breaker mechanism implemented on the JPT service to protect it from load spikes was found to have been incorrectly designed resulting in the service being impacted for all users when triggered by a single unavailable database. Corrective Actions: The following corrective actions have been identified and will be implemented by the end of July 2025: the offending queries have been reviewed and optimized to mitigate the impact of unexpected large batch jobs the JPT circuit breaker has been revised to apply in a targeted manner and not disrupt service for all users the offending customer database entity is being temporarily segregated and monitored

Read the full incident report →

Started Jun 13, 2025, 07:16 PM UTC· resolved Jun 13, 2025, 07:22 PM UTC

1. resolved Jun 13, 2025, 08:33 PM UTC

   In the US2 and EU2 Data Centers, access to Concur Expense, Concur Request, and Concur Travel through the SAP Concur website and SAP Concur mobile app was below expected level. After logging in, affected users may have encountered a home page with tile alerts indicating service disruption. As the Incident Response Team was being assembled, services self-recovered. We have verified that service performance is stable and will now resolve the incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete.

2. resolved Jun 16, 2025, 06:31 PM UTC

   In the US2 Data Center, access to Concur Expense, Concur Request, and Concur Travel through the SAP Concur website and SAP Concur mobile app was below expected level. After logging in, affected users may have encountered a home page with tile alerts indicating service disruption. After further investigation, we determined this issue did not cause any significant disruption to EU2 customers. A subsequent review of our monitoring and logging systems show that the errors our team detected in EU2 were specifically related to the maintenance window for Analysis/Intelligence services occurring at the same time of this incident. This issue has been removed from the EU2 dashboard on Concur Open, EU2 customers will receive no further notifications.

3. resolved Jun 26, 2025, 08:32 AM UTC

   Impact as Reported: In the US2 Data Center, access to Concur Expense, Concur Request, and Concur Travel through the SAP Concur website and SAP Concur mobile app was below expected level. After logging in, affected users may have encountered a home page with tile alerts indicating service disruption. Root cause: The Incident Response Team is investigating a transient spike of errors from two services invoked when serving the SAP Concur home page. We will provide an update once the root cause is identified. Corrective Actions: Corrective actions will be determined once root cause has been fully identified.

4. resolved Sep 11, 2025, 02:02 PM UTC

   Impact as Reported: In the US2 Data Center, access to Concur Expense, Concur Request, and Concur Travel through the SAP Concur website and SAP Concur mobile app was below expected level. After logging in, affected users may have encountered a home page with tile alerts indicating service disruption. Root cause: The incident response team has identified that an update to a network component part of the home page service inadvertently introduce a defect causing increased memory utilization that had not manifested during pre-production testing. The increased memory utilization briefly caused some of the calls processed thorugh the home page service to time out and result in customer disurption until the service capacity automatically scaled up and restored service.

Read the full incident report →

Started Jun 12, 2025, 03:20 AM UTC· resolved Jun 12, 2025, 04:42 AM UTC

1. resolved Jun 12, 2025, 09:54 AM UTC

   In the EU2 Data Center, travel bookings in the new Concur Travel through the SAP Concur website were 70% below expected level. Affected users might have experienced long processing times and error “You have been successfully logged in, but unfortunately, one or more of our services appears to be unavailable at the moment” when trying to complete car, hotel, air and rail bookings. Additionally, logins from the SAP Concur mobile app were below expected level as well. As the Incident Response Team was being assembled, the service automatically self-recovered. We have verified that service performance is stable and will now resolve the incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete.

2. resolved Jun 26, 2025, 08:57 AM UTC

   Impact as Reported: In the EU2 Data Center, Travel bookings in the new Concur Travel through the SAP Concur website were 70% below expected level. Affected users might have experienced long processing times and error “You have been successfully logged in, but unfortunately, one or more of our services appears to be unavailable at the moment” when trying to complete car, hotel, air and rail bookings. Additionally, logins from SAP Concur mobile app were below expected level as well. Root cause: A version update on a database supporting the SAP Concur travel functionality despite prolonged testing ahead of deployment resulted in an unexpected performance degradation for a legacy store procedure under specific load types, briefly causing resource exhaustion on said database and consequently a degradation for the travel service. The issue has been addressed by updating the affected store procedure to address the inefficiencies that resulted in the performance degradation. Corrective Actions: The following corrective and preventive actions have been identified: The impacted store procedure has been updated in all SAP Concur environments to address the potential performance issue; Additional monitoring is being enabled on the impacted database to enable better visibility and troubleshooting on potential performance issues

Read the full incident report →

Started Jun 10, 2025, 05:32 PM UTC· resolved Jun 10, 2025, 05:46 PM UTC

1. resolved Jun 10, 2025, 05:45 PM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Jun 10, 2025, 06:01 PM UTC

   In the APJ1 Data Center, access to Concur Services through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have encountered the following error page when attempting to access www.apj1.concursolutions.com, “Sorry, Concur is currently unavailable.". Services have returned to normal operating levels. We will continue monitoring performance for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.

3. resolved Jun 10, 2025, 06:14 PM UTC

   In the APJ1 Data Center, access to Concur Services through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have encountered the following error page when attempting to access www.apj1.concursolutions.com, “Sorry, Concur is currently unavailable." As the Incident Response Team (IRT) was gathering, the issue self-recovered. We have verified that service performance is stable and will now resolve the incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete.

4. resolved Jun 24, 2025, 02:50 PM UTC

   In the APJ1 Data Center, access to Concur Services through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have encountered the following error page when attempting to access www.apj1.concursolutions.com, “Sorry, Concur is currently unavailable." An update was inadvertently deployed to the production instance of a gateway service. The update was intended for a staging instance that is used to validate the release prior to moving to production. This resulted in users failing to connect to the CTE application and receiving an error stating that Concur was unavailable. The Incident Response Team reverted the update to restore the connectivity to CTE. Corrective Actions: The gateway service will add a confirmation step to verify the destination of the update to ensure it is only released to staging instances and not directly into production.

Read the full incident report →

Started Jun 10, 2025, 07:24 AM UTC· resolved Jun 10, 2025, 07:46 AM UTC

1. resolved Jun 10, 2025, 09:18 AM UTC

   In the US2 Data Center, Travel bookings and Invoice submits through the SAP Concur website and SAP Concur mobile app were below expected level. Affected travel users may have experienced a slowness when attempting to search or book flight, while invoice users were facing error: "Sorry, but there has been an error processing your request.", when attempting to submit their invoice request. As the Incident Response Team (IRT) was gathering, the issue self-recovered. We have verified that service performance is stable and will now resolve this incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete.

2. resolved Jun 24, 2025, 02:48 PM UTC

   In the US2 Data Center, Travel bookings and Invoice submits through the SAP Concur website and SAP Concur mobile app were below expected level. Affected travel users may have experienced a slowness when attempting to search or book flight, while invoice users were facing error: "Sorry, but there has been an error processing your request.", when attempting to submit their invoice request. The root cause of the incident appears to be related database software version upgrade that occurred over the weekend prior to the incident. This upgrade impacted the way certain queries were optimised and executed. In this case, we observed a specific stored procedure taking longer to execute and consuming significant amount of resources. As a result, this and other procedures started causing significant blocking on a shared core database, resulting in a temporary degradation for services depending on it. Corrective Actions: The offending stored procedure has been isolated and is undergoing an optimisation process. Additionally, alerting and notification configurations have been reviewed to improve observability and response.

Read the full incident report →

Started May 14, 2025, 07:00 AM UTC· resolved May 14, 2025, 11:01 AM UTC

1. resolved May 14, 2025, 08:28 AM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved May 14, 2025, 09:03 AM UTC

   In the EU2 Data Center, logins and use of SAP Concur services through SAP Concur website is below expected level. Affected users may intermittently be unable to login or experience error “Sorry, something went wrong” after being logged in. Alternatively, the users might get error “Sorry, something went wrong with this task” when trying to create an expense report. The Incident Response Team (IRT) has been engaged and are investigating. Our next scheduled update will be in one hour or sooner, should a significant change occur.

3. resolved May 14, 2025, 10:09 AM UTC

   In the EU2 Data Center, logins and use of SAP Concur services is below expected level through the SAP Concur website. Affected users may intermittently be unable to login or experience error “Sorry, something went wrong” after being logged in. Alternatively, the users might get error “Sorry, something went wrong with this task” or “There has been an error processing your request” when trying to create an expense report or request, or miss a print button in Expense module. Since our last update the IRT has restarted the application service tier, which failed to restore the service. The IRT is in the process of restarting the user login functionality server tier. Our next scheduled update will be in one hour or sooner, should a significant change occur.

4. resolved May 14, 2025, 11:05 AM UTC

   In the EU2 Data Center, logins and use of SAP Concur services is below expected level through the SAP Concur website. Affected users may intermittently be unable to login or experience error “Sorry, something went wrong” after landing the homepage. Alternatively, the users might get error “Sorry, something went wrong with this task” or “There has been an error processing your request” when trying to create an expense report or request, or miss a print button in Expense module. Workaround: The affected users may try to refresh the homepage several times after they receive the error in order to access the services. Since our last update the IRT continues to restart the user login functionality server tier while checking service performance.

5. resolved May 14, 2025, 11:18 AM UTC

   In the EU2 Data Center, logins and use of SAP Concur services was below expected level through the SAP Concur website. Affected users may have intermittently been unable to login or would experience error “Sorry, something went wrong” after landing the homepage. Alternatively, the users might got error “Sorry, something went wrong with this task” or “There has been an error processing your request” when trying to create an expense report or request, or miss a print button in Expense module. While service performance is now operating at normal levels, we will continue monitoring performance for the next 15 minutes to verify stability. Once verified as stable, the incident will be resolved.

6. resolved May 14, 2025, 11:31 AM UTC

   In the EU2 Data Center, logins and use of SAP Concur services were below expected level through the SAP Concur website. Affected users may have intermittently been unable to login or would experience error “Sorry, something went wrong” after landing the homepage. Alternatively, the users might got error “Sorry, something went wrong with this task” or “There has been an error processing your request” when trying to create an expense report or request, or miss a print button in Expense module. The Incident Response Team restarted the user login functionality server tier which restored the service for all the affected users. We have verified that service performance is stable and will now resolve this incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete.

7. resolved May 26, 2025, 04:00 PM UTC

   Impact as Reported: In the EU2 Data Center, logins and use of SAP Concur services is below expected level through the SAP Concur website. Affected users may intermittently be unable to login or experience error “Sorry, something went wrong” after landing the homepage. Alternatively, the users might get error “Sorry, something went wrong with this task” or “There has been an error processing your request” when trying to create an expense report or request, or miss a print button in Expense module Root cause: The root cause of the incident has been determined to be an issue with the infrastructure controlling internal connectivity across micro-services responsible for the authentication workflow. Due to a set of nodes unexpectedly found in a non-responsive state, a percentage of traffic was not being correctly routed resulting in intermittent errors or time outs. Once the issue was identified the nodes were refreshed to restore service.What caused the impacted nodes to be in an unresponsive state is still being investigated, additional logging and instrumentation will be configured to enable deeper data collection in the event the same issue would re-occurs in the future. Corrective Actions: Various initiatives have been identified to enhance monitoring and alerting in order to improve detection for this type of scenarios and decrease reaction and recovery times.

Read the full incident report →

Started Mar 24, 2025, 07:05 PM UTC· resolved Mar 24, 2025, 07:35 PM UTC

1. resolved Mar 24, 2025, 08:52 PM UTC

   In the US2 Data Center, Concur Compleat service through the SAP Concur website was unavailable. Affected TMCs may have encountered an error when attempting to access Compleat Control. Additionally, PNRs may have not been processing as expected. As the Incident Response Team (IRT) was gathering, services recovered. We have verified that service performance is stable and will now resolve this incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete.

2. resolved Apr 14, 2025, 12:39 PM UTC

   Impact as Reported: In the US2 Data Center, Concur Compleat service through the SAP Concur website was unavailable. Affected TMCs may have encountered an error when attempting to access Compleat Control. Additionally, PNRs may have not been processing as expected. Root cause: The database instance was blocking several queries from running which prevented users from being able to login and use Compleat services. The Incident Response team identified that a script was executed by the support team but had been left in an incomplete state. The script was waiting on user action to complete the query. Leaving the query incomplete caused the database to put other queries on hold until the script finishes. The support team completed the user action to remediate the issues. Corrective Actions: The following corrective actions were identified Support to work with engineering to review the results of executing database scripts and monitor production Engineering to update documentation for more guidance on what to review when executing scripts to ensure they complete successfully.

Read the full incident report →

Started Feb 11, 2025, 01:45 AM UTC· resolved Feb 11, 2025, 04:00 PM UTC

1. resolved Feb 11, 2025, 04:10 PM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Feb 11, 2025, 04:33 PM UTC

   In the US2 and EU2 Data Centers, GRDC receipt image processing is unavailable via the SAP Concur mobile app. Affected users may experience latency after clicking "Take Photo", followed by "Processing" without advancement in the workflow when attempting to upload a receipt. The Incident Response Team is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.

3. resolved Feb 11, 2025, 05:25 PM UTC

   In the US2 and EU2 Data Centers, GRDC receipt image processing is unavailable via the SAP Concur mobile app. Affected users may experience latency after clicking "Take Photo", followed by "Processing" without advancement in the workflow when attempting to upload a receipt. The Incident Response Team (IRT) has determined the outage is related to a third party vendor outage, and is currently working with the vendor to resolve. Our next scheduled update will be in one hour or sooner should a significant change occur.

4. resolved Feb 11, 2025, 06:25 PM UTC

   In the US2 and EU2 Data Centers, GRDC receipt image processing is unavailable via the SAP Concur mobile app. Affected users may experience latency after clicking "Take Photo", followed by "Processing" without advancement in the workflow when attempting to upload a receipt. The Incident Response Team (IRT) continues their investigation with the third party vendor. Additionally, the team is investigating the potential for internal actions that may help to alleviate impact. Our next scheduled update will be in one hour or sooner should a significant change occur.

5. resolved Feb 11, 2025, 07:15 PM UTC

   In the US2 and EU2 Data Centers, GRDC receipt image processing is unavailable via the SAP Concur mobile app. Affected users may experience latency after clicking "Take Photo", followed by "Processing" without advancement in the workflow when attempting to upload a receipt. The Incident Response Team (IRT) is currently performing a configuration update and testing the update to determine if impact can be resolved via internal actions. If testing should yield positive results, the update will be deployed via a hotfix. Our next scheduled update will be in one hour or sooner should a significant change occur.

6. resolved Feb 11, 2025, 08:13 PM UTC

   In the US2 and EU2 Data Centers, GRDC receipt image processing is unavailable via the SAP Concur mobile app. Affected users may experience latency after clicking "Take Photo", followed by "Processing" without advancement in the workflow when attempting to upload a receipt. The Incident Response Team (IRT) continues their work to complete the configuration change and testing to confirm if this configuration change will resolve impact. Upon completion and validation of successful testing, the team will take action to deploy the hotfix. Our next scheduled update will be in one hour or sooner should a significant change occur.

7. resolved Feb 11, 2025, 08:27 PM UTC

   In the US2 and EU2 Data Centers, GRDC receipt image processing was unavailable via the SAP Concur mobile app. Affected users may have experienced latency after clicking "Take Photo", followed by "Processing" without advancement in the workflow when attempting to upload a receipt. Services have returned to normal operating levels. We will continue monitoring performance for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.

8. resolved Feb 11, 2025, 08:48 PM UTC

   In the US2 and EU2 Data Centers, GRDC receipt image processing is unavailable via the SAP Concur mobile app. Affected users may experience latency after clicking "Take Photo", followed by "Processing" without advancement in the workflow when attempting to upload a receipt. We have observed a new disruption to our services during the monitoring period. The Incident Response Team (IRT) is investigating the issue. Our next scheduled update will be in one hour or sooner should a significant change occur.

9. resolved Feb 11, 2025, 09:58 PM UTC

   In the US2 and EU2 Data Centers, GRDC receipt image processing is unavailable via the SAP Concur mobile app. Affected users may experience latency after clicking "Take Photo", followed by "Processing" without advancement in the workflow when attempting to upload a receipt. The Incident Response Team (IRT) received notification that the third party vendor restored service. After a brief recovery period, impact to the service returned. The IRT continued their mitigation plan completing the configuration change, however testing yielded unsuccessful results. The IRT is engaging additional resources to investigate a potential network issue. Our next scheduled update will be in two hours or sooner should a significant change occur.

10. resolved Feb 11, 2025, 11:45 PM UTC

    In the US2 and EU2 Data Centers, GRDC receipt image processing is unavailable via the SAP Concur mobile app. Affected users may experience latency after clicking "Take Photo", followed by "Processing" without advancement in the workflow when attempting to upload a receipt. The Incident Response Team (IRT) is working on the configuration change and running tests to complete the deployment of the fix, which will restore the service. They have completed the deployment in US2 and are working on completing the fix in EU2. Our next scheduled update will be in two hours or sooner should a significant change occur.

11. resolved Feb 12, 2025, 12:35 AM UTC

    In the US2 and EU2 Data Centers, GRDC receipt image processing was unavailable via the SAP Concur mobile app. Affected users may have experienced latency after clicking "Take Photo", followed by "Processing" without advancement in the workflow when attempting to upload a receipt. Services have returned to normal operating levels. We will continue monitoring performance for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.

12. resolved Feb 12, 2025, 12:37 AM UTC

    In the US2 and EU2 Data Centers, GRDC receipt image processing was unavailable via the SAP Concur mobile app. Affected users may have experienced latency after clicking "Take Photo", followed by "Processing" without advancement in the workflow when attempting to upload a receipt. The Incident Response Team made a configuration change which restored the service. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete

13. resolved Mar 03, 2025, 11:05 AM UTC

    Impact as Reported: In the US2 and EU2 Data Centers, GRDC receipt image processing was unavailable via the SAP Concur mobile app. Affected users may have experienced latency after clicking "Take Photo", followed by "Processing" without advancement in the workflow when attempting to upload a receipt. Root cause: An outage for the primary third party time stamp service provider used by Concur caused the GRDC receipt image processing service to became unavailable for end users. The incident response team switched to an alternative time stamp service provider to restore service. Corrective Actions: The following corrective actions have been identified: monitoring on the feature is being enhanced to ensure earlier detection of service degradation and prompter response time stamp service providers are being reviewed to ensure stable service offering.

Read the full incident report →