OpenPath Outage History

OpenPath is up right now

Pingoru has recorded 24 incidents for OpenPath: 3 in the last 12 months and 0 in the last 90 days.

Source: status.openpath.io

24incidents recorded
3last 12 months
0last 90 days
15 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking OpenPath in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 19 (0%)

Incidents, newest first

Minor January 22, 2026 Automated incident report 1d 13h

Started Jan 22, 2026, 03:46 AM UTC· resolved Jan 23, 2026, 05:19 PM UTC

  1. investigating Jan 22, 2026, 03:46 AM UTC

    Monitor System Down Checking, on Collection System Down Checking, did not run successfully. 5 request(s) ran and 1 test(s) failed.

  2. monitoring Jan 22, 2026, 03:52 AM UTC

    There was a spike in response times for under a minute, no systems were affected and response times are normal. We are currently monitoring.

  3. resolved Jan 23, 2026, 05:19 PM UTC

    This has been resolved

Read the full incident report →

Notice January 5, 2026 Automated incident report 2m

Started Jan 05, 2026, 08:37 PM UTC· resolved Jan 05, 2026, 08:40 PM UTC

  1. investigating Jan 05, 2026, 08:37 PM UTC

    Monitor System Down Checking, on Collection System Down Checking, did not run successfully. 5 request(s) ran and 0 test(s) failed.

  2. resolved Jan 05, 2026, 08:40 PM UTC

    This issue was a false positive while switching environments to new updated 3DS features.

Read the full incident report →

Major November 18, 2025 Automated incident report 6h Enterprise Portal, Account Portal, Shopify Checkout, Transaction Portal

Started Nov 18, 2025, 06:31 PM UTC· resolved Nov 19, 2025, 12:32 AM UTC

  1. investigating Nov 18, 2025, 06:31 PM UTC

    Monitor System Down Checking, on Collection System Down Checking, did not run successfully. 5 request(s) ran and 0 test(s) failed.

  2. identified Nov 18, 2025, 06:38 PM UTC

    We have identified an issue with our user interfaces, we are in the process of restoring them right now.

  3. identified Nov 18, 2025, 07:29 PM UTC

    We are still trying to restore the customer user interfaces and are currently working with Microsoft Azure to restore the systems.

  4. monitoring Nov 18, 2025, 10:41 PM UTC

    The issue has been resolved and we are currently monitoring the system as well as reviewing what caused the issue initally.

  5. resolved Nov 19, 2025, 12:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 24, 2025 Automated incident report 6h 36m

Started Sep 24, 2025, 06:25 PM UTC· resolved Sep 25, 2025, 01:01 AM UTC

  1. investigating Sep 24, 2025, 06:25 PM UTC

    Monitor System Down Checking, on Collection System Down Checking, did not run successfully. 5 request(s) ran and 0 test(s) failed.

  2. resolved Sep 25, 2025, 01:01 AM UTC

    Azure Routing Issue

Read the full incident report →

Notice September 11, 2025 Automated incident report 12h 42m

Started Sep 11, 2025, 05:02 AM UTC· resolved Sep 11, 2025, 05:45 PM UTC

  1. investigating Sep 11, 2025, 05:02 AM UTC

    Monitor System Down Checking, on Collection System Down Checking, did not run successfully. 5 request(s) ran and 0 test(s) failed.

  2. identified Sep 11, 2025, 03:54 PM UTC

    An issue was identified with a server in our environment that has having issues connecting to other services. The issue did not cause any downtime for any of the services.

  3. monitoring Sep 11, 2025, 03:57 PM UTC

    We have solved the service connections issue with the affected server and will continue to monitor.

  4. resolved Sep 11, 2025, 05:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 6, 2025 Automated incident report 6h 25m Enterprise Portal, Transaction API, Platform API, Account Portal and 4 more

Started May 06, 2025, 09:24 AM UTC· resolved May 06, 2025, 03:50 PM UTC

  1. investigating May 06, 2025, 09:24 AM UTC

    Monitor System Down Checking, on Collection System Down Checking, did not run successfully. 0 request(s) ran and 0 test(s) failed.

  2. investigating May 06, 2025, 03:49 PM UTC

    We are currently looking into this automated incident report. At the moment is looks like the monitoring system was failing from 2:13AM and resolved itself at 3:01AM.

  3. resolved May 06, 2025, 03:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 20, 2025 Automated incident report 1d 19h

Started Mar 20, 2025, 08:35 PM UTC· resolved Mar 22, 2025, 03:40 PM UTC

  1. investigating Mar 20, 2025, 08:35 PM UTC

    Monitor System Down Checking, on Collection System Down Checking, did not run successfully. 5 request(s) ran and 2 test(s) failed.

  2. resolved Mar 22, 2025, 03:40 PM UTC

    Standard Patch Releases

Read the full incident report →

Major February 8, 2025 Automated incident report 30d 2h

Started Feb 08, 2025, 12:35 PM UTC· resolved Mar 10, 2025, 03:25 PM UTC

  1. investigating Feb 08, 2025, 12:35 PM UTC

    Monitor System Down Checking, on Collection System Down Checking, did not run successfully. 5 request(s) ran and 0 test(s) failed.

  2. investigating Feb 08, 2025, 04:46 PM UTC

    We are aware of ongoing issues with the Transaction API and are actively working to identify the cause.

  3. resolved Mar 10, 2025, 03:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 4, 2025 Issue with amount being passed to PaymentLync 4h 40m

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

  1. resolved Feb 04, 2025, 11:30 AM UTC

    There are a high amount of declines for NSF on transactions flowing through PaymentLync.

  2. postmortem Feb 07, 2025, 04:27 PM UTC

    Technical Issue Report #27 Summary On February 4, 2025, at 3:45 AM, a technical issue occurred, lasting 4.5 hours, which resulted in misplaced decimals in transaction amounts and led to customer overcharges. All affected transactions have been reversed. The issue stemmed from a format change related to a new 3DS feature. It was detected at 7:45 AM through merchant decline alerts, and a hotfix was deployed by 8:25 AM. In total, nine customers experienced financial impact, while 178 were unable to transact. Post-Mortem 1. Incident Summary 1. Date & Time of Incident: Tuesday February 4th, 2025 at 3:45 AM 2. Duration: 4.5 Hours 3. Impact: Consumers using the OpenPath and PaymentLync were being charged too much due to decimal placement 4. Severity Level: **Critical** 5. Reported By: Jason Martin at OpenPath 2. Root Cause Analysis 1. What Happened? An OpenPath update was released which had several new updates, one of the updates for PaymentLync caused Consumers to be billed two decimal places over, so $25.00 would become $2,500.00. 2. Root Cause: To facilitate the new 3DS data only feature with PaymentLync, OpenPath changed the Format of the amount being sent from 2500.0 to 2500. This change was made because at the time of testing the 3DS endpoint was only accepting integers. 3. Detection & Response 1. How Was It Detected? We received automated alerts of Multiple declines from Merchants at 7:45 AM and began investigating, when he found the issue. 2. Initial Response Actions: At 8:10 AM we met with the development team and created a hotfix which was deployed and live at 8:25 AM. 3. Time to Detection: 4 Hours 4. Time to Resolution: 20 Minutes 4. Impact Assessment 1. Users Affected: 9 Customers financially impacted which needed to be made whole again. 178 Customers that were unable to transact but were not financially Impacted. 2. Systems Affected: OpenPath PaymentLync Transaction API 3. Business Impact: Revenue loss, Reputational Damage for OpenPath, PaymentLync and Merchants.

Read the full incident report →

Minor December 30, 2024 Automated incident report 15d 14h

Started Dec 30, 2024, 10:05 AM UTC· resolved Jan 15, 2025, 12:31 AM UTC

  1. investigating Dec 30, 2024, 10:05 AM UTC

    Monitor System Down Checking, on Collection System Down Checking, did not run successfully. 5 request(s) ran and 0 test(s) failed.

  2. identified Jan 02, 2025, 04:14 PM UTC

    This is a continued monitoring issue from the previous week. The issue is not affecting transactions, or any systems and the alerts are false positives. The resolution from last week solved the issue happening multiple times a day; however, is still triggering once to twice a day. We currently have some monitoring fixes pending review a deployment today January 2nd, 2025.

  3. resolved Jan 15, 2025, 12:31 AM UTC

    This issue has now been resolved.

Read the full incident report →

Minor December 26, 2024 Automated incident report 5h 6m Platform API

Started Dec 26, 2024, 06:45 PM UTC· resolved Dec 26, 2024, 11:51 PM UTC

  1. investigating Dec 26, 2024, 06:45 PM UTC

    Monitor System Down Checking, on Collection System Down Checking, did not run successfully. 5 request(s) ran and 0 test(s) failed.

  2. identified Dec 26, 2024, 11:47 PM UTC

    Intermittent Platform API error was identified and our dev team worked in the fix

  3. resolved Dec 26, 2024, 11:51 PM UTC

    Healthcheck configuration in our Platform AppService has been successfully updated. The service is now fully operational and functioning as expected.

Read the full incident report →

Minor December 20, 2024 Automated incident report 3d 11h

Started Dec 20, 2024, 04:40 PM UTC· resolved Dec 24, 2024, 04:20 AM UTC

  1. investigating Dec 20, 2024, 04:40 PM UTC

    Monitor System Down Checking, on Collection System Down Checking, did not run successfully. 5 request(s) ran and 0 test(s) failed.

  2. identified Dec 24, 2024, 04:19 AM UTC

    We have deployed a new group of API servers to our existing groups of API servers. This new group is occasionally producing false positives with our automated monitoring systems. We are currently working on correcting this issue; however, at this time it is not affecting any of our services.

  3. resolved Dec 24, 2024, 04:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 21, 2024 Automated incident report 8d

Started Nov 21, 2024, 08:02 PM UTC· resolved Nov 29, 2024, 08:59 PM UTC

  1. investigating Nov 21, 2024, 08:02 PM UTC

    Monitor System Down Checking, on Collection System Down Checking, did not run successfully. 5 request(s) ran and 0 test(s) failed.

  2. investigating Nov 21, 2024, 08:28 PM UTC

    We are currently reviewing this issue and will update as soon as we have more information available.

  3. investigating Nov 21, 2024, 08:43 PM UTC

    To restore services as quickly as possible, we temporarily diverted traffic. At this time, all systems appear to be functioning as expected. We will now conduct a deeper investigation into the issue and provide updates here as soon as new information becomes available.

  4. resolved Nov 29, 2024, 08:59 PM UTC

    This issue has been resolved, for the Postmortem please see: https://asset.openpath.io/download/pdf/connection-pool-exhaustion-issue.pdf

Read the full incident report →

Notice November 21, 2024 Automated incident report 4h 7m Transaction API

Started Nov 21, 2024, 01:25 PM UTC· resolved Nov 21, 2024, 05:32 PM UTC

  1. investigating Nov 21, 2024, 01:25 PM UTC

    Monitor System Down Checking, on Collection System Down Checking, did not run successfully. 5 request(s) ran and 2 test(s) failed.

  2. investigating Nov 21, 2024, 05:30 PM UTC

    A 504 timeout occurred between Azure Application Gateway and the Transactions API App Service, which had stopped and failed to auto-restart. I manually restarted it and added a Health Check to ensure auto-restart in the future. No service was impacted, as requests were handled by active VM instances.

  3. resolved Nov 21, 2024, 05:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2024 Automated incident report 8h 58m

Started Nov 18, 2024, 10:30 AM UTC· resolved Nov 18, 2024, 07:29 PM UTC

  1. investigating Nov 18, 2024, 10:30 AM UTC

    Monitor System Down Checking, on Collection System Down Checking, did not run successfully. 5 request(s) ran and 2 test(s) failed.

  2. resolved Nov 18, 2024, 07:29 PM UTC

    Upon investigation, there was a 20 second timeout on the Microsoft Azure Application Gateway, this timeout did not impact any systems.

Read the full incident report →