中断网络切换超时
Pending
受影响的组件
API v2
- monitoring
我们正在密切监测影响签证象征性服务的问题。 虽然交易代号已稳定下来,但我们继续观察系统性能,并与Visa合作,以确保完全可靠.
- resolved
这一事件从2026年10月22日中午12点(协调世界时18:00)解决.
自动翻译自官方事件更新。
62 Tokenex incidents · 2022年10月 — official updates, affected components, duration and resolution details.
我们正在密切监测影响签证象征性服务的问题。 虽然交易代号已稳定下来,但我们继续观察系统性能,并与Visa合作,以确保完全可靠.
这一事件从2026年10月22日中午12点(协调世界时18:00)解决.
自动翻译自官方事件更新。
在2026年10月13日11:12 PM到11:16 PM EDT(03:12–03:16 UTC于10月14日)之间,一些用户无法到达pciapply.com达标门户,看到一个错误的页面而不是登录页面. 我们的监控马上发现了这个问题, 服务在几分钟内就恢复了, 没有用户的行动。 我们查明了原因,并采取步骤来尽量减少再次发生的危险.
自动翻译自官方事件更新。
2026年10月13日,从11:12 PM到11:16 PM EDT(10月14日03:12–03:16 UTC),pciapply.com达标门户短暂无法访问,用户看到一个错误的页面而不是登录页面. 原因是例行的自动系统更新重启了服务器. 服务在没有干预的情况下完全恢复.
自动翻译自官方事件更新。
各小组目前正在调查影响我们通用Tokenization(TokenEx)平台的服务问题。 更新情况一旦公布,将公布于此.
一项措施已经执行,我们正在监测结果.
在延长的监测期间没有观察到其他问题。 此事已决. 如有问题,请联系支援组.
自动翻译自官方事件更新。
在协调世界时2026年10月6日09:13至09:36之间,AI支付情报门户经历了断断续续的问题,一些用户可能难以访问或使用该平台. 这个问题已经解决了,该平台自协调世界时09:36起正常运行. 我们的团队继续密切监测,以确保它保持稳定。 其他IXPAY服务,包括付费管弦乐团和通用交响乐团,没有受到影响。 我们为任何不便而道歉。 如果你有问题或还有问题 请联系支援组.
自动翻译自官方事件更新。
各小组目前正在调查影响Aperia合规平台的服务问题。 更新情况一旦公布,将公布于此.
截至UTC17:24,已恢复对Aperia合规平台的访问. 我们的小组正在继续监测业绩,以确保稳定,一旦这一问题得到全面解决,我们将提供又一最新情况"
影响Aperia合规平台的问题已经解决,自协调世界时17:24起恢复正常服务. 我们的技术小组将继续分析这一事件,以确定其根本原因.
自动翻译自官方事件更新。
从3:09到3:14 时间,用户在访问PCI应用门户网站时可能观察到了性能退化或超时. 截至3:14 PM CT,系统一直在正常参数范围内运行.
自动翻译自官方事件更新。
中央下午1点57分 时间,我们开始观察超时 尝试加载"Get Started"页面 在 Aperia 遵守脚本显示器产品。 团队调查并解决了这个问题,本页目前从中央时间下午2:33开始再次工作.
自动翻译自官方事件更新。
付款处理不受影响。 交易、API端点和结算正常运行。 第三方供应商的服务中断时断时续地影响我们的支助门户和售票系统。 自09:50 CEST起,访问一直不一致:登录可能偶尔成功,后一瞬间再次失败,页面可能会缓慢加载或出错. 在这些期间,顾客提交的入场券可能无法到达我们的支援团队,我们可能无法查看或回应已经排入队的入场券. 由于中断时断时续,一些门票可能会通过,但不会立即被支援队看到. 成功登录并不意味着由于断断续续的问题而解决了这个问题. 服务稳定后我们会确认 供应商已经将中断追踪到一个内部登录服务的问题。 这不是安全事件,也没有影响客户数据。 未提供估计解决时间。 我们从供应商那里收到最新消息,并将在从第三方得到消息时张贴我们自己的最新消息.
第三方已经解决了他们在过去23个小时内所遇到的断断续续的问题。 现在,你们应该能够通过客户门户不断成功地提交案件,我们的支助队能够不断查看和更新罚单。 谢谢你的耐心.
自动翻译自官方事件更新。
2026年9月15日,在协调世界时14:04至14:05之间,由于失去生产数据库节点,付费管弦乐平台被短暂占用了约36秒. 服务自动恢复,正常处理于协调世界时14:05恢复.
自动翻译自官方事件更新。
We are currently investigating intermittent issues with the TokenEx APIv2 endpoint. Teams are engaged, and updates will be posted here as they become available.
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.
我们正在调查一个可能影响到3D安全引擎的问题,它似乎来自我们平台之外,主要影响万事达卡交易。 我们的小组正在积极调查局势,并将在获得更多信息后提供最新情况.
我们的调查显示,这个问题起源于 Mastercard 侧面, 并导致 Mastercard 3D 安全认证失败。 我们已与Mastercard联系,并积极监测他们的情况。 只有Mastercard 3D安全认证受到影响. 一旦获得更多信息,我们将提供进一步的最新资料。 欲了解最新消息,请查阅相关状态页:status.3dsecurity.io.
我们不再观察Mastercard认证错误,可以确认正常业务已经恢复。 Mastercard尚未正式确认事件已解决. 我们将继续密切监测局势,并随时提供进一步的最新资料.
我们可以确认,这个问题已经得到解决。 该服务正常运行,我们没有看到任何进一步的影响。 我们将继续监测局势,以确保稳定.
自动翻译自官方事件更新。
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.
Our teams are continuing to work on resolving the issue. We will provide further updates as they become available.
Transaction processing have recovered to normal levels but reporting is still impacted. Our team is investigating the network issues with our provider.
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.
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.
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.
Data synchronization has completed, and users should now see current transaction data in the portal and dashboards. All systems are operating within normal parameters.
We are observing intermittent service availability issues affecting the TokenEx APIs in the US region. Teams are currently engaged and investigating.
The issue has been identified, and teams are addressing. Most services, with the exception of APIv2, are once again within normal operational parameters.
Services have stabilized as of 10:40 am Central Time. Teams are continuing to monitor.
This incident has been resolved.
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.
We are continuing to investigate this issue.
Created Incident instead of Maintenance Activity.
We identified an issue resulting in a brief service interruption impacting a subset of customers on our platform. Normal operations have now resumed, and all affected systems have recovered. Our team remains engaged and is actively investigating the situation to gather pertinent details and determine the underlying root cause. We will continue to monitor system health closely. We are currently not expecting any further interruption. Please make sure that the service is fully functional on your side as well. If you experience any ongoing irregularities, please contact our support team.
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.
This incident is resolved. Teams have confirmed system stability, and no further impacts are expected.
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.
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.
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.
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.
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.
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.
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.
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.
Teams have identified the potential cause of the issue and are actively remediating.
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.
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.