Fastspring driftsforstyrrelser

1. 20. oktober 2026 kl. 11.22 UTCinvestigating

   Nogle asynkron Data API rapport job mislykkes på grund af en access- nægtet fejl, når du skriver rapporter til S3 opbevaring spand. Spørgsmålet begyndte omkring 18: 06 UTC, 19. oktober og er intermitterende, med nogle job fortsætter med at fuldføre med succes. Flere butikker er berørt, og en service genstart har ikke løst problemet. Holdet efterforsker.

2. 20. oktober 2026 kl. 11.55 UTCresolved

   Et fix er blevet anvendt, og datatjenesten er blevet genstartet. Problemet synes at være løst, og holdet vil fortsætte med at overvåge tjenesten for at sikre, at rapporteringsjob er afsluttet med succes.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 15. oktober 2026 kl. 23.50 UTCinvestigating

   Vi undersøger et problem, der kan påvirke webhook levering for nogle sælgere. Når problemet er løst, berørte webkroge vil blive prøvet igen i henhold til vores standard genprøve proces. Vi vil levere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 16. oktober 2026 kl. 00.39 UTCresolved

   Problemet er blevet løst, og berørte netkroge bliver prøvet igen.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 18. september 2026 kl. 12.14 UTCinvestigating

   Vi undersøger en forsinkelse, der påvirker behandlingen af nogle planlagte abonnementsfornyelser. Vores team arbejder aktivt på at behandle de forsinkede fornyelser og bestemme årsagen. Vi vil give en opdatering som mere information bliver tilgængelig.

2. 18. september 2026 kl. 13.37 UTCinvestigating

   Abonnementsmeddelelser og rebeller oplever i øjeblikket en forsinkelse. Vi arbejder på at behandle alle fornyelser og sælgere bør tillade en afdragsfri periode for alle abonnementer til at behandle.

3. 18. september 2026 kl. 23.09 UTCresolved

   Alle verserende abonnementsmeddelelser og rebeller for september 18, 2026, er blevet behandlet med succes. Da behandlingen blev afsluttet inden for UTC-dagen, er der ingen forventet indvirkning på regnskaber eller tidsplaner. Vi undskylder forsinkelsen.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 17. september 2026 kl. 09.35 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, der forhindrer nogle sælgere i at skabe brugerdefinerede ordrer. Vores team undersøger aktivt problemet og arbejder på at genoprette funktionaliteten så hurtigt som muligt. Vi vil give yderligere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 17. september 2026 kl. 12.02 UTCresolved

   Spørgsmålet om at forhindre nogle sælgere i at skabe brugerdefinerede ordrer er blevet løst. Vi følger fortsat situationen for at sikre stabilitet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 16. september 2026 kl. 16.20 UTCinvestigating

   Meddelelse fra Google: Vi er klar over et problem med Android CreateButton API, Android IsReadyToPay API, Android LoadPaymentData API, Secure Payment Authentication (SPA), Web CreateButton API, Web IsReadyToPay API, og Web LoadPaymentData API påvirker et flertal af brugere. Vi vil give en opdatering af 16 sep, 2026, 3: 20 PM UTC detaljer, når vi forventer at løse problemet. Bemærk venligst, at denne afviklingstid er et skøn og kan ændre sig. De berørte brugere er i stand til at få adgang til Android CreateButton API, Android IsReadyToPay API, Android LoadPaymentData API, Secure Payment Authentication (SPA), Web CreateButton API, Web IsReadyToPay API, og Web LoadPaymentData API, men ser fejlmeddelelser, høj latency, og / eller anden uventet adfærd. Yderligere oplysninger: https: / / pay.google.com / status / hændelser / gQJsjf662F7KwPiynqav

2. 16. september 2026 kl. 17.01 UTCresolved

   Denne hændelse er blevet løst. http: / / pay.google.com / status / hændelser / gQJsjf662F7KwPiynqav

Automatisk oversat fra den officielle hændelsesopdatering.

1. 26. maj 2026 kl. 08.57 UTCresolved

   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.

1. 9. april 2026 kl. 20.04 UTCinvestigating

   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.

2. 9. april 2026 kl. 20.05 UTCidentified

   The issue has been identified.

3. 15. april 2026 kl. 18.37 UTCresolved

   This incident has been resolved.

1. 26. februar 2026 kl. 22.32 UTCresolved

   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.

1. 28. november 2025 kl. 14.41 UTCinvestigating

   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.

2. 28. november 2025 kl. 17.48 UTCinvestigating

   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.”

3. 28. november 2025 kl. 22.52 UTCresolved

   Operations and services are back to normal.

1. 18. november 2025 kl. 14.24 UTCinvestigating

   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.

2. 18. november 2025 kl. 14.56 UTCresolved

   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.

1. 20. oktober 2025 kl. 19.06 UTCinvestigating

   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.

2. 20. oktober 2025 kl. 20.34 UTCmonitoring

   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.

3. 20. oktober 2025 kl. 21.45 UTCresolved

   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.

1. 20. oktober 2025 kl. 07.34 UTCinvestigating

   Our cloud service provider is currently having issues with its service which is impacting our platform.

2. 20. oktober 2025 kl. 07.50 UTCinvestigating

   We are continuing to investigate this issue.

3. 20. oktober 2025 kl. 08.28 UTCidentified

   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.

4. 20. oktober 2025 kl. 09.24 UTCidentified

   We continue to work with AWS to restore service

5. 20. oktober 2025 kl. 10.01 UTCmonitoring

   AWS services are being restored, but there may be delays in buyer emails or webhooks. We continue to monitor the situation

6. 20. oktober 2025 kl. 11.45 UTCmonitoring

   Email and webhook delivery continues to be impacted by the AWS incident. We will continue to monitor

7. 20. oktober 2025 kl. 17.41 UTCresolved

   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.

1. 16. oktober 2025 kl. 16.54 UTCinvestigating

   FastSpring has received alerts confirming that PayPal is down. We will continue to monitor and will update you with changes.

2. 16. oktober 2025 kl. 17.33 UTCresolved

   We are no longer seeing the error in our logs and PayPal orders are completing successfully

1. 8. august 2025 kl. 20.13 UTCinvestigating

   As a precautionary measure, we are temporarily disabling Klarna due to a processor issue

2. 12. september 2025 kl. 18.39 UTCresolved

   This incident has been resolved.

1. 1. august 2025 kl. 14.37 UTCinvestigating

   Paypal is currently experiencing checkout issues. Please see https://www.paypal-status.com/incident/production for more information.

2. 1. august 2025 kl. 15.24 UTCresolved

   Paypal is reporting the incident as resolved, see https://www.paypal-status.com/history/production

1. 17. juni 2025 kl. 17.04 UTCresolved

   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

1. 19. februar 2025 kl. 19.33 UTCresolved

   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.

1. 11. februar 2025 kl. 11.10 UTCinvestigating

   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.

2. 11. februar 2025 kl. 11.49 UTCmonitoring

   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.

3. 11. februar 2025 kl. 14.52 UTCresolved

   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.

1. 21. november 2024 kl. 13.02 UTCinvestigating

   PayPal appears to be down. We are investigating.

2. 21. november 2024 kl. 13.25 UTCresolved

   This issue has been resolved by PayPal.

1. 16. oktober 2024 kl. 20.04 UTCinvestigating

   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

2. 16. oktober 2024 kl. 20.33 UTCmonitoring

   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.

3. 16. oktober 2024 kl. 21.10 UTCresolved

   We see consistent signs of recovery for Paypal orders. Payments are operational.