TokenEx Outage History

TokenEx is up right now

TokenEx had 15 outages in the last 2 years totaling 88h 48m of downtime — averaging 0.6 incidents per month.

There were 15 TokenEx outages since January 28, 2026 totaling 88h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tokenex.com

Notice October 6, 2026

Intermittent issues with AI Payments Intelligence Portal

Detected by Pingoru
Oct 06, 2026, 07:13 AM UTC
Resolved
Oct 06, 2026, 07:13 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 06, 2026, 10:23 AM UTC

    Between 09:13 and 09:36 UTC on October 6, 2026, the AI Payments Intelligence Portal experienced intermittent issues, and some users may have had trouble accessing or using the platform. The issue has been resolved, and the platform has been operating normally since 09:36 UTC. Our team continues to monitor it closely to make sure it stays stable. Other IXOPAY services, including Payment Orchestration and Universal Tokenization, were not affected. We apologize for any inconvenience. If you have questions or are still having trouble, please contact our Support team.

Read the full incident report →

Notice October 1, 2026

Aperia Compliance Service Issues

Detected by Pingoru
Oct 01, 2026, 04:35 PM UTC
Resolved
Oct 01, 2026, 07:02 PM UTC
Duration
2h 26m
Timeline · 3 updates
  1. investigating Oct 01, 2026, 04:35 PM UTC

    Teams are currently investigating service issues affecting the Aperia Compliance platform. Updates will be posted here as they become available.

  2. monitoring Oct 01, 2026, 05:38 PM UTC

    As of 17:24 UTC, access to the Aperia Compliance platform has been restored. Our teams are continuing to monitor performance to ensure stability, and we will provide another update once this issue is fully resolved."

  3. resolved Oct 01, 2026, 07:02 PM UTC

    The issue affecting the Aperia Compliance platform has been resolved, and normal service has resumed as of 17:24 UTC. Our technical teams will continue to analyze the incident to determine the underlying cause.

Read the full incident report →

Notice September 30, 2026

Performance Issues - PCI Apply

Detected by Pingoru
Sep 30, 2026, 08:09 PM UTC
Resolved
Sep 30, 2026, 08:09 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 30, 2026, 08:25 PM UTC

    From 3:09 PM to 3:14 PM Central US Time, users may have observed degraded performance or timeouts when accessing the PCI Apply portal. As of 3:14 PM CT, systems have been operating within normal parameters.

Read the full incident report →

Notice September 24, 2026

Script Monitor "Get Started" Page Not Loading

Detected by Pingoru
Sep 24, 2026, 06:57 PM UTC
Resolved
Sep 24, 2026, 06:57 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 24, 2026, 08:26 PM UTC

    At 1:57 PM Central Time, we began observing timeouts when attempting to load the "Get Started" page within the Aperia Compliance script monitor product. Teams investigated and resolved the issue, and this page is now working again as of 2:33 PM Central Time.

Read the full incident report →

Notice September 15, 2026

Brief Service Interruption

Detected by Pingoru
Sep 15, 2026, 06:04 PM UTC
Resolved
Sep 15, 2026, 06:04 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 21, 2026, 05:17 PM UTC

    On 15 September 2026, between 14:04 and 14:05 UTC, the payment orchestration platform was briefly unavailable for approximately 36 seconds due to the loss of a production database node. Service recovered automatically and normal processing resumed at 14:05 UTC.

Read the full incident report →

Major August 6, 2026

TokenEx APIv2 Issues

Detected by Pingoru
Aug 06, 2026, 08:12 PM UTC
Resolved
Aug 06, 2026, 09:06 PM UTC
Duration
53m
Timeline · 2 updates
  1. investigating Aug 06, 2026, 08:12 PM UTC

    We are currently investigating intermittent issues with the TokenEx APIv2 endpoint. Teams are engaged, and updates will be posted here as they become available.

  2. resolved Aug 06, 2026, 09:06 PM UTC

    This incident has been resolved. Users might have observed intermittent latency or timeouts when calling the TokenEx APIv2 endpoint between 20:02 and 20:09 UTC. Since 20:09 UTC, all systems have operating within normal parameters.

Read the full incident report →

Minor July 15, 2026

Increased 3DS Mastercard errors

Detected by Pingoru
Jul 15, 2026, 07:36 AM UTC
Resolved
Jul 15, 2026, 09:05 AM UTC
Duration
1h 28m
Timeline · 4 updates
  1. investigating Jul 15, 2026, 07:36 AM UTC

    We are investigating a potential issue affecting the 3D Secure Engine that appears to originate outside of our platform and is primarily impacting Mastercard transactions. Our team is actively investigating the situation and will provide updates as more information becomes available.

  2. identified Jul 15, 2026, 07:58 AM UTC

    Our investigation indicates that the issue originates on the Mastercard side and is causing Mastercard 3D Secure authentications to fail. We have contacted Mastercard and are actively monitoring the situation with them. Only Mastercard 3D Secure authentications are affected. We will provide further updates as more information becomes available. For the latest information, please refer to the related status page: status.3dsecure.io.

  3. monitoring Jul 15, 2026, 08:34 AM UTC

    We are no longer observing Mastercard authentication errors and can confirm that normal operations have resumed. Mastercard has not yet officially confirmed the incident as resolved. We will continue to monitor the situation closely and provide further updates as they become available.

  4. resolved Jul 15, 2026, 09:05 AM UTC

    We can confirm that the issue has been resolved. The service is operating normally, and we have not observed any further impact. We will continue to monitor the situation to ensure stability.

Read the full incident report →

Major June 19, 2026

Payment Orchestration Service Disruption

Detected by Pingoru
Jun 19, 2026, 09:36 AM UTC
Resolved
Jun 19, 2026, 02:28 PM UTC
Duration
4h 52m
Timeline · 7 updates
  1. investigating Jun 19, 2026, 09:36 AM UTC

    We are currently experiencing a service disruption affecting Payment Orchestration. Teams are engaged and actively investigating. Further updates will follow as more information becomes available.

  2. identified Jun 19, 2026, 11:08 AM UTC

    Our teams are continuing to work on resolving the issue. We will provide further updates as they become available.

  3. monitoring Jun 19, 2026, 12:35 PM UTC

    Transaction processing have recovered to normal levels but reporting is still impacted. Our team is investigating the network issues with our provider.

  4. identified Jun 19, 2026, 01:29 PM UTC

    Teams are continuing to work toward full service restoration. Transactions are processing successfully, however, they are not yet visible in the admin UI, dashboards, search, reporting, or export mechanisms. This data will become visible once services are fully restored.

  5. monitoring Jun 19, 2026, 01:32 PM UTC

    Transaction processing is fully operational and payments continue to be processed normally. The impact is limited to visibility, which means recent transactions may not currently appear in the Admin UI or Dashboards even though they are being processed successfully. Our teams are continuing to work on restoring the affected services and further updates will follow.

  6. monitoring Jun 19, 2026, 01:54 PM UTC

    Search/reporting functionality has been restored, and data is currently synchronizing. Users should begin to see transaction data in the portal and dashboards. Teams are continuing to monitor while synchronization completes and to ensure ongoing stability.

  7. resolved Jun 19, 2026, 02:28 PM UTC

    Data synchronization has completed, and users should now see current transaction data in the portal and dashboards. All systems are operating within normal parameters.

Read the full incident report →

Major June 18, 2026

TokenEx Service Issues

Detected by Pingoru
Jun 18, 2026, 03:28 PM UTC
Resolved
Jun 18, 2026, 04:03 PM UTC
Duration
35m
Timeline · 4 updates
  1. investigating Jun 18, 2026, 03:28 PM UTC

    We are observing intermittent service availability issues affecting the TokenEx APIs in the US region. Teams are currently engaged and investigating.

  2. identified Jun 18, 2026, 03:32 PM UTC

    The issue has been identified, and teams are addressing. Most services, with the exception of APIv2, are once again within normal operational parameters.

  3. monitoring Jun 18, 2026, 03:50 PM UTC

    Services have stabilized as of 10:40 am Central Time. Teams are continuing to monitor.

  4. resolved Jun 18, 2026, 04:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 15, 2026

Universal Tokenization Maintenance: US Region - June 2026

Detected by Pingoru
Jun 15, 2026, 08:48 PM UTC
Resolved
Jun 16, 2026, 11:20 PM UTC
Duration
1d 2h
Timeline · 3 updates
  1. investigating Jun 15, 2026, 08:48 PM UTC

    The Universal Tokenization Production Environment (US) will undergo scheduled Production Patching on Thursday, June 18th, from 5am - 7am CST (11:00 UTC - 13:00 UTC). Impact: All production services are expected to remain fully operational throughout this maintenance window. If you have any questions or concerns about this scheduled maintenance, please contact our support team.

  2. investigating Jun 15, 2026, 08:49 PM UTC

    We are continuing to investigate this issue.

  3. resolved Jun 16, 2026, 11:20 PM UTC

    Created Incident instead of Maintenance Activity.

Read the full incident report →

Notice May 14, 2026

TokenEx APIv2 Service Interruption

Detected by Pingoru
May 14, 2026, 10:26 PM UTC
Resolved
May 14, 2026, 11:20 PM UTC
Duration
53m
Timeline · 2 updates
  1. investigating May 14, 2026, 10:26 PM UTC

    We are investigating a service interruption that impacted the TokenEx APIv2 endpoints in our US region. Impact was observed from 4:40 pm to 4:54 pm US Central Time. Services are currently stable, and technical teams are engaged.

  2. resolved May 14, 2026, 11:20 PM UTC

    This incident is resolved. Teams have confirmed system stability, and no further impacts are expected.

Read the full incident report →

Notice May 11, 2026

Elevated Transaction Processing Errors

Detected by Pingoru
May 11, 2026, 02:30 PM UTC
Resolved
May 12, 2026, 04:14 PM UTC
Duration
1d 1h
Timeline · 7 updates
  1. investigating May 11, 2026, 02:30 PM UTC

    We are currently investigating elevated errors and intermittent connectivity issues for IXOPAY services. Our team is engaged and actively analyzing the impact on our transaction processing and overall service availability.

  2. identified May 11, 2026, 02:57 PM UTC

    We have identified the underlying cause of the elevated transaction processing errors and intermittent connectivity issues affecting IXOPAY services. Our team is actively working on implementing a fix and restoring full service stability. We continue to monitor the environment closely and will provide further updates as progress is made.

  3. monitoring May 11, 2026, 03:07 PM UTC

    Mitigation measures have been implemented for the elevated transaction processing errors and intermittent connectivity issues affecting IXOPAY services. Transaction processing and service availability have stabilized, and our team is currently monitoring the environment closely to ensure continued normal operations.

  4. monitoring May 11, 2026, 03:32 PM UTC

    The issue causing elevated transaction processing errors and intermittent connectivity issues affecting IXOPAY services has been resolved. Services are operating normally again, and our team is continuing to monitor the environment closely to ensure ongoing stability.

  5. monitoring May 12, 2026, 02:36 AM UTC

    We are currently investigating elevated errors and intermittent connectivity issues for IXOPAY services. Our team is engaged and actively analyzing the impact on our transaction processing and overall service availability.

  6. monitoring May 12, 2026, 03:07 AM UTC

    The issue causing elevated transaction processing errors and intermittent connectivity issues affecting IXOPAY services has been resolved. Services are operating normally again, and our team is continuing to monitor the environment closely to ensure ongoing stability.

  7. resolved May 12, 2026, 04:14 PM UTC

    The incident affecting IXOPAY services has been fully resolved. Our monitoring has confirmed stable operations, and all services are functioning normally at this time. We apologize for the inconvenience and appreciate your patience during this time.

Read the full incident report →

Notice February 12, 2026

Brief Firewall VM degradation in US datacenter

Detected by Pingoru
Feb 12, 2026, 12:11 PM UTC
Resolved
Feb 12, 2026, 12:11 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 12, 2026, 01:03 PM UTC

    This morning at 6:11 AM CST(12:11 PM UTC), we experienced an issue with the active firewall VM in our US datacenter, which triggered an automatic failover event. The resulting service interruption lasted less than one minute. Systems have been operating normally since the failover completed. We continue to monitor the environment to ensure stability.

Read the full incident report →

Major January 28, 2026

TokenEx APIv1 service degradation

Detected by Pingoru
Jan 28, 2026, 02:55 PM UTC
Resolved
Jan 28, 2026, 04:12 PM UTC
Duration
1h 16m
Timeline · 4 updates
  1. investigating Jan 28, 2026, 02:55 PM UTC

    We are investigating intermittent response failures on the TokenEx APIv1 endpoints in the US region, initially observed at 8:38 am Central Time. We will provide updates here as investigation continues.

  2. identified Jan 28, 2026, 03:25 PM UTC

    Teams have identified the potential cause of the issue and are actively remediating.

  3. monitoring Jan 28, 2026, 03:31 PM UTC

    A fix has been implemented and the team is monitoring the results. We believe the issue to be resolved as of 9:28 am CT.

  4. resolved Jan 28, 2026, 04:12 PM UTC

    The issue has been resolved and the TokenEx APIv1 endpoints are operating normally. The cause was identified to be a planned configuration change, which was reverted. Monitoring since the fix was applied has not shown any additional failures. A post-mortem review will be conducted internally to avoid reoccurrence in the future.

Read the full incident report →