55 Fastspring incidents · 2021年10月 — official updates, affected components, duration and resolution details.
一些同步的数据 API 报告任务由于在向 S3 存储桶写报告时存在拒绝访问错误而失败 。 该问题从协调世界时10月19日18:06左右开始并时断时续,一些工作继续顺利完成. 多个商店受到影响,服务重启并未解决问题. 调查组正在调查.
已应用了固定,并重新启动了数据服务。 这个问题似乎已经解决,小组将继续监测这项服务,以确保报告工作顺利完成.
自动翻译自官方事件更新。
我们正在调查一个可能影响一些卖家的网络销售的问题。 一旦问题得到解决,受影响的网络呼声将根据我们的标准重试程序进行再试。 一旦获得更多信息,我们将提供最新资料.
问题已经解决,正在重新审理受影响的网络用户.
自动翻译自官方事件更新。
我们正在调查影响一些预定续订的手续的延误。 我们的团队正在积极努力处理拖延的延期,并确定原因。 一旦获得更多信息,我们将提供最新情况.
订阅通知和汇票目前出现延误。 我们正在处理所有续约事宜,销售者应允许所有订阅费有一个宽限期处理.
2026年9月18日所有待定的订阅通知和汇票均已成功办理. 由于处理工作是在协调世界时当天完成的,预计不会对账户或时间表产生影响。 我们为延迟道歉.
自动翻译自官方事件更新。
我们目前正在调查一个阻止一些销售商订立海关订单的问题。 我们的小组正在积极调查这一问题并努力尽快恢复功能。 一旦获得更多信息,我们将提供进一步的最新资料.
阻止一些卖方订立海关订单的问题已经得到解决。 我们正在继续监测局势,以确保稳定.
自动翻译自官方事件更新。
来自谷歌的通知 : 我们知道Android CreateButton API,Android IsReadyTOPay API,Android LoadPaymentData API,安全支付认证(SPA),Web CreateButton API,Web IsReadyTOPay API,和Web LoadPaymentData API存在问题,影响到大多数用户. 我们将在协调世界时2026年9月16日3:20提供最新消息, 请注意,该决议的时间是估计的,可能会有变化。 受影响的用户可以访问Android CreateButton API,Android IsReadyTopay API,Android LoadPaymentData API,安全支付认证(SPA),Web CreateButton API,Web IsReadyTopay API,和Web LoadPaymentData API,但正在看到出错消息,高纬度和/或其他出乎意料的行为. 详情访问:https://pay.google.com/status/incidents/gQJsjf662F7KwPyiNqav
这一事件已经得到解决。 详情请访问https://pay.google.com/status/incidents/gQJsjf662F7KwPyiNqav
自动翻译自官方事件更新。
We observed a drop in Amazon order completion rates and investigated the issue. However, the issue is now resolved. Amazon orders are currently processing normally, and the error is no longer being observed.
We’re currently experiencing issues with some UPI transactions. Payments made using VPA handles such as @okhdfcbank, @okaxis, and @okybl via GPay and PhonePe may fail or be declined. Payments using other UPI apps or different VPA handles are working normally. Our partner banks are actively working to resolve this issue. We’ll share updates as soon as more information becomes available.
The issue has been identified.
This incident has been resolved.
During a routine maintenance release, from 12:25 pm PT to 02:00 pm PT, our system encountered an error where some buyer emails failed to be sent. The change has been reverted, and we can confirm buyer emails are successfully being sent.
We are experiencing degraded performance with checkout loading, including slow or failed loads, due to increased Black Friday traffic. Engineering is treating this as a critical issue and is actively investigating.
We are no longer seeing latency or failed checkout loads, but our engineering team is continuing to actively investigate the earlier performance degradation. We will provide updates as more information becomes available.”
Operations and services are back to normal.
Pix payments are currently unavailable due to an ongoing issue with CloudFlare (https://www.cloudflarestatus.com/). No other impact is known at this time, but we continue to monitor.
Our Engineers are not seeing any continuing impact. Ebanx confirmed on their status page that their systems are now functioning normally. Cloudflare has also confirmed that the issue is resolved and things are back to how it was pre-incident. We consider this issue resolved.
We are currently experiencing delays in processing webhooks and auto-generated emails. Our team is working with Amazon Web Services (AWS) to identify the cause and restore normal performance as quickly as possible. Updates will be provided as we learn more.
Emails have been successfully sent, though webhooks are still experiencing delays. We expect these delays to resolve, but unfortunately, we cannot provide an exact timeframe. Rebills are continuing to be processed and will require a few more hours to complete.
Webhook latency is gradually returning to normal levels. All subscription rebills are currently processing, and we will continue to monitor the system for any further issues.
Our cloud service provider is currently having issues with its service which is impacting our platform.
We are continuing to investigate this issue.
We are currently experiencing an issue caused by an ongoing AWS outage that is impacting the FastSpring platform. As a result, sellers may be unable to log in to their FastSpring accounts, and buyer checkout experiences may also be affected on stores hosted through FastSpring. Our engineering team is actively monitoring the situation and working with AWS to restore full functionality as soon as possible. We will provide updates here as more information becomes available. Thank you for your patience and understanding.
We continue to work with AWS to restore service
AWS services are being restored, but there may be delays in buyer emails or webhooks. We continue to monitor the situation
Email and webhook delivery continues to be impacted by the AWS incident. We will continue to monitor
All services are operating normally, except for a delay in processing rebills. Our team is actively working to resolve this and ensure all affected transactions are completed as soon as possible.
FastSpring has received alerts confirming that PayPal is down. We will continue to monitor and will update you with changes.
We are no longer seeing the error in our logs and PayPal orders are completing successfully
As a precautionary measure, we are temporarily disabling Klarna due to a processor issue
This incident has been resolved.
Paypal is currently experiencing checkout issues. Please see https://www.paypal-status.com/incident/production for more information.
Paypal is reporting the incident as resolved, see https://www.paypal-status.com/history/production
On June 16th 2025 around 1350 PST our servers started experiencing degraded performance due to unusual traffic patterns. We identified the root cause and took actions to resolve the degradation, mitigating the symptoms around 1420 PST
Between 1:50 AM and 5:50 AM PT, we observed a decline in PayPal orders, preventing some customers from completing their transactions. The issue was caused by a system-related problem on PayPal's end. As of now, all orders are processing normally.
We are aware that some sellers are experiencing API rate limiting issues, which are disrupting day-to-day business operations. FastSpring is actively investigating this as a priority and working towards a resolution. We will provide updates as soon as more information becomes available.
We’ve identified a 30-minute window where almost all API calls were blocked, from 11:36 PM on 02.10 to 12:06 AM on 02.11. However, after this period, API traffic appears to be functioning normally. At this time, the issue does not seem to be ongoing, but we are continuing to investigate the cause of the blockage during that specific window. We will provide further updates as we gather more information. Thank you for your patience.
We’ve identified a 30-minute window where almost all API calls were blocked, from 11:36 PM on 02.10 to 12:06 AM on 02.11. However, after this period, API traffic appears to be functioning normally. At this time, the issue does not seem to be ongoing, but we are continuing to investigate the cause of the blockage during that specific window. We will provide further updates as we gather more information. Thank you for your patience.
PayPal appears to be down. We are investigating.
This issue has been resolved by PayPal.
We are investigating the impact of a Paypal outage starting Oct 16, 17:35 UTC. You may also refer to Paypal's status page here - https://www.paypal-status.com/incident/production
We are seeing signs of recovery. Paypal is reporting that they have mitigated the issue and are also seeing recovery. We will continue to monitor.
We see consistent signs of recovery for Paypal orders. Payments are operational.
