Fastspring outage history

Some asynchronous Data API report jobs are failing due to an access-denied error when writing reports to the S3 storage bucket. The issue began at approximately 18:06 UTC, October 19th and is intermittent, with some jobs continuing to complete successfully. Multiple stores are affected, and a service restart has not resolved the issue. The team is investigating.

A fix has been applied, and the data-service has been restarted. The issue appears to be resolved, and the team will continue to monitor the service to ensure report jobs are completing successfully.

We are investigating an issue that may affect webhook delivery for some sellers. Once the issue is resolved, affected webhooks will be retried according to our standard retry process. We will provide updates as more information becomes available.

The issue has been resolved and affected webhooks are being retried.

We are investigating a delay affecting the processing of some scheduled subscription renewals. Our team is actively working to process the delayed renewals and determine the cause. We will provide an update as more information becomes available.

Subscription notifications and rebills are currently experiencing a delay. We are working on processing all renewals and sellers should allow a grace period for all subscription billings to process.

All pending subscription notifications and rebills for September 18, 2026, have been successfully processed. Because processing was completed within the UTC day, there is no anticipated impact on accounts or schedules. We apologize for the delay.

We are currently investigating an issue that is preventing some sellers from creating custom orders. Our team is actively investigating the issue and working to restore the functionality as soon as possible. We will provide further updates as more information becomes available.

The issue preventing some sellers from creating custom orders has been resolved. We are continuing to monitor the situation to ensure stability.

Notification from Google: We're aware of a problem with Android CreateButton API, Android IsReadyToPay API, Android LoadPaymentData API, Secure Payment Authentication (SPA), Web CreateButton API, Web IsReadyToPay API, and Web LoadPaymentData API affecting a majority of users. We will provide an update by Sep 16, 2026, 3:20 PM UTC detailing when we expect to resolve the problem. Please note that this resolution time is an estimate and may change. The affected users are able to access Android CreateButton API, Android IsReadyToPay API, Android LoadPaymentData API, Secure Payment Authentication (SPA), Web CreateButton API, Web IsReadyToPay API, and Web LoadPaymentData API, but are seeing error messages, high latency, and/or other unexpected behavior. For more information visit: https://pay.google.com/status/incidents/gQJsjf662F7KwPyiNqav

This incident has been resolved. For more information visit 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.