Elevated API errors
Timeline · 1 update
- resolved Aug 01, 2026, 12:45 PM UTC
From 12:04 to 12:26 UTC on August 1st, we saw elevated error rates and response times with the Stripe API. The issue is resolved and we will continue to monitor.
Taskade had 48 outages in the last 2 years totaling 99h 4m of downtime — averaging 2 incidents per month.
There were 48 Taskade outages since September 19, 2025 totaling 99h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.
From 12:04 to 12:26 UTC on August 1st, we saw elevated error rates and response times with the Stripe API. The issue is resolved and we will continue to monitor.
We're currently investigating elevated card authorization errors starting 02:25 UTC related to an issuer in Mexico. We'll post an update soon.
As of 03:24 UTC, elevated card authorization errors related to an issuer in Mexico which is impacting card transactions in Mexico have recovered. We're continuing to validate that this issue is fully resolved.
From 02:25 - 03:24 UTC, we saw elevated card authorization errors related to an issuer-side degradation in Mexico. This is now resolved.
From 09:59 UTC to 10:13 UTC on July 21, 2026, we saw elevated error rates on BLIK payments affecting multiple customers. This issue is now resolved. We confirmed that the issue was upstream and was restored without Stripe actions.
We're currently investigating elevated error rates and response times with payments. We'll post an update soon.
We're currently seeing a degradation of the Blik payment method. Our partner has identified the cause and is working on a fix.
From 19:40 to 22:10 UTC, we saw elevated errors for Blik payment method payments. This is now resolved.
Starting 19:00 UTC we started seeing elevated error rates affecting Issuing API requests, resulting in failing credit card transactions. We've identified the cause and are working to mitigate. We will provide an update when we start seeing recovery.
From 19:00–19:55 UTC on July 17, 2026, Issuing users did not receive real-time authorization request webhooks and experienced declined transactions. All systems have recovered and are operating normally.
We’re observing elevated 3DS errors for Mastercard transactions starting 07:00 UTC. We are engaging with the Mastercard team and we will provide an update as soon as we have more information.
We are starting to see improvement in the elevated 3D Secure errors affecting Mastercard transactions. The impact still continues however Stripe engagement with Mastercard teams continue. We will provide further updates once we have observed recovery.
As of 09:06 UTC, we can confirm that the elevated 3D Secure errors on Mastercard transactions have recovered following certificate rotation by Mastercard. We're continuing to validate that this issue is fully resolved and will provide further updates once we have observed sustained recovery.
From 2026-07-15 07:00:00 UTC to 09:06:00 UTC, we experienced elevated 3D Secure errors on Mastercard transactions due to an expired certificate on the upstream Mastercard service. Mastercard identified and resolved the issue on their end. We have verified that all certificates are now valid and transactions are processing normally.
We're currently investigating a degradation of the WeChat Pay payment method that began at 7:10 UTC. This issue is external to Stripe and is causing increased error rates for transactions processed through the WeChat Pay payment method. We are actively monitoring the situation and will provide updates as more information becomes available.
We’re currently seeing a degradation of the WeChat Pay payment method. Our partner have identified the cause and are working on a fix
WeChat Pay has confirmed they are addressing the issue and it will take some time to implement the fix. We will provide another update in 12 hours, or as new information is discovered.
From 07:10 July 2 to 01:20 July 3 UTC, we saw elevated errors which affected WeChat Pay payment method transactions. This issue has now been resolved by our partner.
We're currently investigating a Partial Service disruption of the P24 payment method that began at 10:52 UTC. This issue is external to Stripe and is causing increased error rates for transactions processed through the P24 payment method. We are actively monitoring the situation and will provide updates as more information becomes available.
From 10:52–11:34 UTC, we saw a partial service disruption of the P24 payment method. This is now resolved.
As of 04:16 UTC, some card transactions in Mexico are experiencing elevated declines due to an issuing bank being temporarily unavailable. We're in touch with the card network and will post an update as soon as they become available.
From 04:16 - 05:00 UTC, some card transactions in Mexico experienced elevated declines due to an issuing bank being temporarily unavailable. This is now resolved.
We’re currently seeing elevated error rates and response times with some Cartes Bancaires payments due to an issuer-side degradation starting 07:23 UTC June 4th. We believe this outage is outside of Stripe's infrastructure. This is likely impacting a number of payment processors. We’re continuing to monitor and will post further updates.
We are continuing to see elevated error rates and response times with some Cartes Bancaires payments due to an issuer-side degradation starting 07:23 UTC June 4th. We are actively monitoring and will provide a further update as more information becomes available.
Between 07:23 UTC on June 4th and 13:51 UTC on June 5th, we saw elevated error rates and response times with some Cartes Bancaires payments. This is now resolved.
We're currently investigating a Partial Service disruption of the Bancontact payment method that began at 13:38 UTC. This issue is external to Stripe and is causing increased error rates for transactions processed through the Bancontact payment method. We are actively monitoring the situation and will provide updates as more information becomes available.
From 13:38–13:53 UTC, we saw a partial service disruption of the Bancontact payment method. This is now resolved.
As of 08:40 UTC, we've seen elevated errors on Pay_by_bank payments. We're continuing to investigate and will post further updates.
Instant payouts in EUR to bank accounts and Bank Transfers payments are experiencing delay and some might fail due to a broader industry issue affecting SEPA Instant. All other payouts, including instant payouts to debit cards, are unaffected. We're investigating and will provide an update once resolved.
Instant payouts in EUR to bank accounts and Bank Transfers payments continue to experience delays due broader industry issues affecting SEPA Instant. All other payouts, including instant payouts to debit cards, remain unaffected. We will provide further updates as soon as possible.
Instant payouts to bank accounts and Bank Transfers payments in Europe continue to experience delays due broader issues affecting SEPA Instant. This issue is also resulting in elevated errors on Pay by Bank payments beginning at 08:40 UTC. All other payouts, including instant payouts to debit cards, remain unaffected. We are continuing to engage with our upstream partners, and will provide further updates as soon as they are available.
Instant payouts in EUR to bank accounts, Pay by Bank payments, and Bank Transfers payments in Europe are now working successfully. There was no impact to other payouts, including instant payouts to debit cards during this time.
We're currently investigating elevated MobilePay errors. We'll post an update soon.
Between 14:18–17:20 UTC May 16th, we saw elevated error rates and response times with MobilePay requests. This is now resolved.
Between 14:18–17:20 UTC May 16th, we saw elevated error rates and response times with MobilePay requests. This is now resolved.
We're currently investigating elevated Apple Pay errors. We'll post an update soon.
Between 02:59–04:58 UTC May 16th, we saw elevated error rates and response times with Apple Pay requests. This is now resolved.
We're currently investigating a Partial Service disruption of the Swish payment method that began at 09:35 UTC. This issue is external to Stripe and is causing increased error rates for transactions processed through the Swish payment method. We are actively monitoring the situation and will provide updates as more information becomes available.
From 09:09–09:48 UTC, we saw a partial service disruption of the Swish payment method. This is now resolved.
We are currently observing elevated Authentication Requests related to issuing banks in the UK and France which is impacting some card transactions.
Between 11:40 UTC and 14:35 UTC we observed elevated Authentication Requests for card transactions in SCA scope. This issue has now been resolved.
We're currently investigating elevated authentication errors affecting some Dashboard features. We'll post an update soon.
From 10:04 - 13:38 UTC, we experienced issues with elevated authentication errors affecting some Dashboard features. This is now resolved.
From 18:15 - 18:34 UTC we saw elevated error rates and response times with requests to Invoicing and Billing-related APIs. This is now resolved.
From 13:42 – 13:55 UTC on April 29th, we saw certificate warning banners on stripe.com and dashboard login caused by a issue with on a downstream provider. This is now resolved.
We're currently experiencing SMS delivery issues in the US, affecting 2-Factor authentication for dashboard users as well as the OTP code for Link and Express users. We'll post an update as soon as we have it.
Since 01:35 UTC, we’ve been experiencing US SMS delivery issues affecting 2FA and OTP codes for Dashboard, Link, Issuing, and Express users. Non-SMS 2FA methods (security keys, authenticator apps) still work. We’re actively monitoring and will update when resolved.
From 01:35 - 05:20 UTC, we saw elevated errors with SMS delivery in the US. This is now resolved.
Due to a processing issue with our banking partner, some Canadian Payouts processed on April 14, 2026 are experiencing a delay of a few hours. We are actively working with our banking partner to resolve this issue to ensure all affected payouts land today.
As of 22:00 UTC, we have identified the root cause with our banking partner and expect affected payouts to land by the end of the day. We will continue to monitor closely and post further updates as needed.
We have confirmed with our banking partner that the issue has been resolved. All impacted Canadian payouts scheduled for April 14th have successfully posted on the same day. Thank you for your patience.
As of 07:55 UTC, we are experiencing issues with the Dashboard, Express Dashboard on all platforms and Mobile surfaces. We’re continuing to investigate and will post further updates. API requests and payment processing are unaffected by this issue.
From 07:55 - 09:59 UTC, we experienced issues with Dashboard, Express Dashboard on all platforms and Mobile surfaces. This is now resolved. API requests and payment processing were unaffected by this issue .
We're currently observing elevated errors on the iDEAL payment method that began at 14:25 UTC. This issue is external to Stripe. We are actively monitoring the situation and will provide updates as more information becomes available.
Between 14:25 - 14:45 UTC there was a disruption with the iDEAL payment method causing increased error rates for iDEAL transactions. The issue was external to Stripe and is now resolved.
We are currently observing elevated errors on Pix payments. Payments are likely affected due to degraded performance reported by Pix. We will continue to monitor the issue and an update will be provided as soon as more information becomes available.
Between 14:13 UTC on the 22nd March and 01:40 UTC on the 23rd March, we observed a service disruption that impacted the Pix payment method. The issue was external to Stripe and is now resolved.