- Detected by Pingoru
- Jun 16, 2026, 05:54 PM UTC
- Resolved
- Jun 17, 2026, 12:07 PM UTC
- Duration
- 18h 12m
Affected: Core APISandbox
Timeline · 5 updates
-
investigating Jun 16, 2026, 05:54 PM UTC
On Tuesday, June 16, 2026, Marqeta engineers detected an issue affecting User/Business/Card API response in the sandbox and a intermittently in production starting at approximately 09:50 PT (17:07 UTC). Our team is aware of the root cause and is actively working to resolve the impact. A follow-up notification with more detail will be sent within 30 minutes.
-
identified Jun 16, 2026, 06:25 PM UTC
On Tuesday, June 16, 2026, Marqeta engineers detected an issue affecting User/Business/Card API response in the sandbox and a intermittently in production starting at approximately 09:50 PT (17:07 UTC). Our team is aware of the root cause and is continuing to actively work to resolve the impact. A follow-up notification with more detail will be sent within 30 minutes.
-
identified Jun 16, 2026, 06:54 PM UTC
On Tuesday, June 16, 2026, Marqeta engineers detected an issue affecting User, Business, and Card API responses in the sandbox and intermittently in production, starting at approximately 09:50 PT (17:07 UTC). Our engineering team has identified the root cause and initiated a hot-fix across all affected environments. We are actively monitoring the fix progress and will provide a further update once the fix is complete and service has been fully verified.
-
monitoring Jun 16, 2026, 08:37 PM UTC
On Tuesday, June 16, 2026, Marqeta engineers detected an issue affecting User, Business, and Card API responses in the sandbox and intermittently in production, starting at approximately 09:50 PT (17:07 UTC). Our engineering team successfully deployed a fix across all affected environments as of 13:09 PT (21:09 UTC). All impacted services have been restored and are currently under active monitoring to ensure full stability. We sincerely apologize for any disruption this caused and appreciate your patience.
-
resolved Jun 17, 2026, 12:07 PM UTC
On Tuesday, June 16, 2026, Marqeta engineers detected an issue affecting User, Business, and Card API responses in the sandbox and intermittently in production, starting at approximately 09:50 PT (17:07 UTC). Our engineering team identified the root cause, successfully deployed a fix across all affected environments, and completed a monitoring period to verify full stability. We sincerely appreciate your patience throughout this incident.
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 03:23 PM UTC
- Resolved
- Jun 15, 2026, 04:21 PM UTC
- Duration
- 57m
Affected: Reporting & Analytics
Timeline · 3 updates
-
investigating Jun 15, 2026, 03:23 PM UTC
On Monday, June 15, 2026, Marqeta engineers detected an issue affecting Visa SMS file delivery starting at approximately 08:01 PT (15:01 UTC). Our team is actively investigating the root cause and assessing the full scope of impact. A follow-up notification with more detail will be sent within 30 minutes.
-
identified Jun 15, 2026, 03:40 PM UTC
On Monday, June 15, 2026, Marqeta engineers detected an issue affecting Visa SMS file delivery starting at approximately 08:01 PT (15:01 UTC). Visa has begun sending the delayed files. Processing will begin as soon as the files are successfully transmitted. We will update this page once we have confirmed the files are processing.
-
resolved Jun 15, 2026, 04:21 PM UTC
On Monday, June 15, 2026, Marqeta engineers detected an issue affecting Visa SMS file delivery starting at approximately 08:01 PT (15:01 UTC). Visa has sent the files, and the processing is underway as expected.
Read the full incident report →
- Detected by Pingoru
- Jun 13, 2026, 06:15 AM UTC
- Resolved
- Jun 13, 2026, 12:15 PM UTC
- Duration
- 6h
Timeline · 1 update
-
resolved Jun 13, 2026, 10:44 AM UTC
At 2:15 AM PDT we identified a disruption in tokenization messages from Mastercard. As of 03:07 AM PDT service began to normalize, and we have since confirmed the receipt of healthy calls from Mastercard. We have engaged Mastercard to provide an explanation and analysis, and we will continue to monitor the connection to ensure stability.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 03:49 PM UTC
- Resolved
- Jun 11, 2026, 04:48 PM UTC
- Duration
- 8d
Affected: Payment Processing
Timeline · 5 updates
-
investigating Jun 03, 2026, 03:49 PM UTC
On Wednesday, June 3, 2026, Marqeta engineers detected an issue affecting Stand-In Processing (STIP) across multiple card networks starting at approximately 08:42 PT. Our team is actively investigating the root cause and assessing the full scope of impact. We will follow up with additional details as soon as more information is available. A follow-up notification with more detail will be sent within 30 minutes.
-
monitoring Jun 03, 2026, 04:12 PM UTC
On Wednesday, June 3, 2026, Marqeta engineers detected an issue affecting Stand-In Processing (STIP) across multiple card networks starting at approximately 08:42 PT. Our team has drained the affected region to stabilize the STIPs, and will continue investigating the root cause.
-
monitoring Jun 04, 2026, 03:57 PM UTC
On Wednesday, June 3, 2026, Marqeta engineers detected an issue affecting Stand-In Processing (STIP) across multiple card networks starting at approximately 08:42 PT. Mitigations remain in place and the root cause is being investigated throughout the day.
-
monitoring Jun 08, 2026, 03:51 PM UTC
On Wednesday, June 3, 2026, Marqeta engineers detected an issue affecting Stand-In Processing (STIP) across multiple card networks starting at approximately 08:42 PT. Our ongoing technical investigation has isolated the root cause of this incident to a degraded physical network connection. We are actively coordinating with our hardware vendor for an expedited component replacement. In the interim, Marqeta engineers are continuously monitoring the affected infrastructure and managing traffic loads to mitigate any further customer impact. We will provide a final resolving update once the hardware replacement is complete and long-term system stability has been fully verified.
-
resolved Jun 11, 2026, 04:48 PM UTC
On Thursday, June 11th, 2026, Marqeta engineers have confirmed that the the physical network connection has been successfully restored, and operations have returned to normal across all affected card networks. Following a period of active monitoring with no further issues observed, long-term system stability has been fully verified.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 07:30 PM UTC
- Resolved
- Jun 02, 2026, 01:49 AM UTC
- Duration
- 6h 19m
Affected: Digital Wallets & Tokenization
Timeline · 6 updates
-
investigating Jun 01, 2026, 07:30 PM UTC
Marqeta engineers detected an intermittent issue affecting Apple Pay in-app card provisioning requests starting at approximately 11:42 PT. Our team is actively investigating the root cause and assessing the full scope of impact. We will update this page with more information in 30 minutes.
-
investigating Jun 01, 2026, 08:00 PM UTC
We are continuing to investigate intermittent errors impacting Apple Pay in-app provisioning requests across multiple regions. The team has identified a possible issue with certificate chain verification related to expired certificates being sent from user devices. Our engineers are actively investigating this issue and have initiated contact with external partners for additional guidance. We will update this page with more information in 30 minutes.
-
investigating Jun 01, 2026, 08:30 PM UTC
We are continuing to investigate intermittent errors impacting Apple Pay in-app provisioning requests across multiple regions. The team has identified a possible issue with certificate chain verification related to expired certificates being sent from user devices. Our engineers are actively investigating this issue and have initiated contact with external partners for additional guidance. We will update this page again in 30 minutes.
-
identified Jun 01, 2026, 09:00 PM UTC
We are continuing to investigate intermittent errors impacting Apple Pay in-app provisioning requests across multiple regions. The team has identified a possible issue with certificate chain verification related to expired certificates being sent from user devices. Our engineers are still actively investigating this issue and are continuing to engage external partners for additional guidance. We will update this page again in 30 minutes.
-
identified Jun 01, 2026, 09:30 PM UTC
We are continuing to investigate intermittent errors impacting Apple Pay in-app provisioning requests across multiple regions. The team has identified a possible issue with certificate chain verification related to expired certificates being sent from user devices. Our engineers are still actively investigating this issue and are continuing to engage external partners for additional context. The next update will take place once engineers have gathered this context and are able to determine next steps.
-
resolved Jun 02, 2026, 01:49 AM UTC
Engineers have observed Apple Pay in-app provisioning errors are no longer occurring.
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 05:14 PM UTC
- Resolved
- May 20, 2026, 08:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 20, 2026, 05:14 PM UTC
Between 12:59 AM and 03:23 AM PDT, an external Mastercard incident caused intermittent errors for customers utilizing MDES token lifecycle actions. This resulted in temporary drops in token notifications and elevated 422 errors on the /v3/digitalwallettokentransitions endpoint due to upstream network issues. All services and webhook notifications have returned to baseline levels and are currently operating normally.
Read the full incident report →
- Detected by Pingoru
- May 15, 2026, 09:12 AM UTC
- Resolved
- May 16, 2026, 03:46 AM UTC
- Duration
- 18h 33m
Affected: Reporting & AnalyticsWebhooks
Timeline · 4 updates
-
investigating May 15, 2026, 09:12 AM UTC
We receive 6 large files from Visa each day containing clearing for Marqeta customers. The last clearing file from the 14th of May has not yet been received from Visa. Impacted customers will have a lower number than normal of clearing webhooks and VSS reports particular to this file are delayed. We have reached out to Visa to understand what has happened, and to ensure the file is sent. Once the file has been received by Marqeta, it will be immediately processed and we will update this incident.
-
identified May 15, 2026, 05:16 PM UTC
Our technical teams have confirmed after engaging Visa that we have processed from our side all files sent so far from Visa. Marqeta is currently addressing a potential delay in the delivery of clearing files from the Visa network., While these files are now being ingested and prioritized through our systems to restore full data visibility, customers may experience temporary discrepancies in data reporting or reconciliation against VSS reports for the impacted date. We are closely monitoring the processing of files sent from Visa side to ensure all records are accurately reflected, We will provide a further update as soon as the processing is complete and data integrity is fully verified.
-
identified May 15, 2026, 11:58 PM UTC
Our teams have been actively monitoring file receipt and processing throughout the day, and we have confirmed that overall clearing volume today exceeds our previous day's totals, with most recent file processed at 14:35 PDT, We are also working to formally reconcile received data against the Visa network summary to provide full confirmation that all expected clearing activity has been recovered, and will provide a further update once reconciliation is complete. We sincerely apologize for any disruption this delay may have caused.
-
resolved May 16, 2026, 03:46 AM UTC
We have successfully processed the final batch of clearing files. Following a thorough reconciliation against the Visa network summary, we can confirm that all expected clearing data is aligned and validated.
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 07:48 AM UTC
- Resolved
- May 13, 2026, 03:10 AM UTC
- Duration
- 19h 22m
Affected: Payment Processing
Timeline · 5 updates
-
identified May 12, 2026, 07:48 AM UTC
Marqeta Engineers have observed elevated STIPs on the Pulse network impacting some cardholders utilizing the Pulse network starting on 11th of May at 10:20 PM PDT. A dedicated response team has been assembled and has identified the technical issue as a processing failure within our systems when encountering a new data pattern originating from the Pulse network. To mitigate the impact and confirm the necessary fix, we have engaged the Pulse team for clarity on this new data behavior, and Pulse has raised an incident from their side to investigate. We will provide an update as soon as we have confirmation of the fix and an estimated time to resolution."
-
identified May 12, 2026, 08:45 AM UTC
To keep our customers updated , we have initiated a joint T.S session with Pulse team, and we are working jointly to investigate the root cause and secure a path for remediation. We will provide an update as soon as we have a confirmed fix or an estimated time to resolution.
-
identified May 12, 2026, 10:20 AM UTC
Our joint technical investigation with the Pulse team has successfully isolated the source of the anomalous data to a single acquiring partner. Pulse is actively working to engage the responsible acquirer to secure a path for remediation. Concurrently, Marqeta is escalating the issue with utmost priority. We will provide an update as soon as we have confirmation of the fix and an estimated time to resolution from Pulse.
-
monitoring May 12, 2026, 04:23 PM UTC
Following up on our previous updates, Pulse has informed us that the responsible acquirer has implemented a change to resolve the root cause, and Marqeta has cross-verified that (STIP) levels returned to normal parameters as of 08:40 AM PT. Our engineering teams will continue to closely observe the stability of the Pulse network to ensure no further disruptions occur for your cardholders, and we will provide a final resolution summary once the monitoring period is successfully complete.
-
resolved May 13, 2026, 03:10 AM UTC
Following a successful monitoring period, Marqeta systems have maintained stable processing since May 12, 08:40 AM PT with no further anomalies detected. We apologize for any impact this may have had on cardholders and appreciate your patience throughout the resolution process.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 12:46 AM UTC
- Resolved
- May 11, 2026, 10:57 PM UTC
- Duration
- 3d 22h
Affected: Payment ProcessingReporting & AnalyticsDigital Wallets & TokenizationRisk & DisputesWebhooksSandbox3DS
Timeline · 15 updates
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 12:29 PM UTC
- Resolved
- May 08, 2026, 12:40 AM UTC
- Duration
- 2d 12h
Affected: Reporting & Analytics
Timeline · 11 updates
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 05:04 PM UTC
- Resolved
- Apr 30, 2026, 05:34 PM UTC
- Duration
- 1d
Affected: 3DS
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Apr 03, 2026, 07:44 PM UTC
- Resolved
- Apr 04, 2026, 04:15 AM UTC
- Duration
- 8h 30m
Affected: Payment Processing
Timeline · 3 updates
-
identified Apr 03, 2026, 07:44 PM UTC
From March 24th, we are experiencing an increase in the rate of declines for card-present transactions using magnetic stripe swipe (magstripe). This may cause cardholder's physical cards to be declined even though the cards and accounts are in good standing. Engineers are working to resolve this issue today. We will update here once this work is complete.
-
identified Apr 04, 2026, 02:55 AM UTC
Engineers are continuing to work to resolve the last few instances of this issue. We will update here once this work is complete.
-
resolved Apr 04, 2026, 04:15 AM UTC
Engineers have resolved the last known instances of this issue.
Read the full incident report →
- Detected by Pingoru
- Apr 02, 2026, 08:31 PM UTC
- Resolved
- Apr 06, 2026, 06:32 PM UTC
- Duration
- 3d 22h
Affected: Core APIPayment ProcessingDigital Wallets & Tokenization
Timeline · 3 updates
-
identified Apr 02, 2026, 08:31 PM UTC
We have observed a database connectivity issue that intermittently impacted Marqeta services on April 1st between 16:04 and 17:56 PST. During this window, some customers may have experienced an elevated amount of STIPs as well as partial disruptions to tokenization and API traffic. Our engineering team has traced the instability to an intermittent database connection failure and has escalated the matter to our third-party vendor for support. We are currently engaged in an active troubleshooting with the vendor's support to isolate the root cause and prevent recurrence by applying a tactical solution. We apologize for any inconvenience this incident may caused, and will periodically provide updates once available.
-
monitoring Apr 03, 2026, 03:10 AM UTC
Following our investigation with the database vendor, a tactical fix was successfully applied at 16:26 PST. Since the implementation of this fix, we have observed a significant improvement in database connection stability and a return to normal service levels. Our engineering team is continuously monitoring the environment to verify the long-term effectiveness of the resolution and ensure overall system stability. We will provide a final update once we have confirmed the issue is fully resolved and appreciate your continued patience.
-
resolved Apr 06, 2026, 06:32 PM UTC
Following an extended period of stability, we have verified that the tactical fix applied to our database environment has fully resolved the connectivity issues and all affected services are performing at baseline levels. We appreciate your patience throughout this event.
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 04:09 PM UTC
- Resolved
- Mar 17, 2026, 07:27 PM UTC
- Duration
- 3h 18m
Affected: ACH Processing
Timeline · 2 updates
-
identified Mar 17, 2026, 04:09 PM UTC
We are currently experiencing delays in bank file delivery for some customers. Engineers have identified the issue and restarted the delivery process. All bank files are expected to be delivered within the next 3 hours.
-
resolved Mar 17, 2026, 07:27 PM UTC
All bank files have been successfully delivered as of 12:17 PM PT. No further delays are expected.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 08:29 PM UTC
- Resolved
- Mar 13, 2026, 12:50 AM UTC
- Duration
- 4h 20m
Affected: Payment Processing
Timeline · 2 updates
-
monitoring Mar 12, 2026, 08:29 PM UTC
Marqeta Engineering team observed network disturbance resulting in STIPS on the Mastercard network, We observed two distinct periods of impact, starting around 11:14 AM and 12:45 PM Pacific Time , the status is currently stable and our team is actively engaged with MasterCard to understand the root cause. We are continuously monitoring the network to ensure stability.
-
resolved Mar 13, 2026, 12:50 AM UTC
We are confirming that the Mastercard network disturbance, which caused two isolated periods of elevated (STIP) earlier today around 11:14 AM and 12:45 PM Pacific Time, is now fully resolved and the service is operating normally. Our engineering team monitored the service to ensure stability with no abnormality observed.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 04:16 PM UTC
- Resolved
- Mar 04, 2026, 05:05 PM UTC
- Duration
- 1d
Affected: ACH Processing
Timeline · 5 updates
-
investigating Mar 03, 2026, 04:16 PM UTC
Marqeta has been notified of an ongoing issue at Federal Reserve Bank ACH Network which may lead to a delay in the processing of ACH transactions. This can affect Direct Deposits, and ACH Origination. We have not yet been provided an ETA for resolution of their issue. We will update you as soon as they indicate that the issue has been resolved and is stable.
-
investigating Mar 03, 2026, 09:32 PM UTC
We are continuing to monitor the ongoing issue at Federal Reserve Bank ACH Network which may lead to a delay in the processing of ACH transactions. We have not yet been provided an ETA for resolution or any workarounds. We will update here as soon as they indicate that the issue has been resolved and is stable.
-
investigating Mar 04, 2026, 01:22 AM UTC
We have processed all ACH transactions received as of this time. However, according to the Federal Reserve Bank's Service Status, there may be continued delays affecting the next set of incoming transactions to the bank. We are continuing to monitor the ongoing issue at the Federal Reserve Bank ACH Network and will provide updates if any further delays are identified.
-
investigating Mar 04, 2026, 02:04 AM UTC
We have processed all ACH transactions received as of this time. However, according to the Federal Reserve Bank's Service Status, there may be continued delays affecting the next set of incoming transactions to the bank. We are continuing to monitor the ongoing issue at the Federal Reserve Bank ACH Network and will provide updates if any further delays are identified.
-
resolved Mar 04, 2026, 05:05 PM UTC
Processing has returned to its normal schedule. We are continuing to monitor the Federal Reserve Bank ACH Network for any reoccurrence and will provide updates if any new delays are identified.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 06:07 PM UTC
- Resolved
- Feb 25, 2026, 06:07 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 25, 2026, 06:07 PM UTC
At approximately 9:23 AM PT, Marqeta customers may have experienced issues logging into Marqeta Dashboard. Engineers quickly identified the root cause and implemented a fix. Customers can now access the Dashboard without issues.
Read the full incident report →
- Detected by Pingoru
- Feb 13, 2026, 01:15 AM UTC
- Resolved
- Feb 13, 2026, 02:35 PM UTC
- Duration
- 13h 19m
Affected: Core API
Timeline · 2 updates
-
monitoring Feb 13, 2026, 01:15 AM UTC
Some Marqeta customers may have experienced elevated API timeouts between 2:00 PM - 3:22 PM PT (22:00 - 23:22 UTC) on Thursday, February 12th. The root cause has been identified, and we do not anticipate any further impact at this time.
-
resolved Feb 13, 2026, 02:35 PM UTC
The issue causing elevated API timeouts between 2:00 PM – 3:22 PM PT (22:00 – 23:22 UTC) on Thursday, February 12th has been fully resolved. The root cause was identified and mitigated, and our engineering team has continued to monitor the environment closely. No further abnormalities have been observed. We do not anticipate any additional impact at this time. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 09:51 AM UTC
- Resolved
- Feb 11, 2026, 02:21 PM UTC
- Duration
- 4h 29m
Affected: Sandbox
Timeline · 2 updates
-
investigating Feb 11, 2026, 09:51 AM UTC
Affected customers using the 2.0 simulation suite will be unable to use the simulations/cardtransactions/ and simulations/directdeposits/ apis, receiving a 503 response. We are escalating to the Product owners, we will update when they have identified the issue.
-
resolved Feb 11, 2026, 02:21 PM UTC
This has now been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 06, 2026, 08:45 PM UTC
- Resolved
- Feb 13, 2026, 10:25 PM UTC
- Duration
- 7d 1h
Affected: Payment Processing
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 07:01 PM UTC
- Resolved
- Feb 02, 2026, 07:30 PM UTC
- Duration
- 28m
Affected: Payment Processing
Timeline · 3 updates
-
investigating Feb 02, 2026, 07:01 PM UTC
At approximately 10:29 AM PT Marqeta engineers observed an elevated amount of STIPs. We are currently investigating the issue. The next update will be at 11:30 AM PT.
-
monitoring Feb 02, 2026, 07:06 PM UTC
Engineers have diverted traffic from the impacted area. Customers should no longer be impacted. We will continue to monitor the situation and provide updates when new information becomes available.
-
resolved Feb 02, 2026, 07:30 PM UTC
Engineers have confirmed that the increase in STIPs occurred between 10:29 AM PT - 10:35 AM PT due to a networking issue in one region. It is now resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 27, 2026, 05:51 PM UTC
- Resolved
- Jan 27, 2026, 06:06 PM UTC
- Duration
- 14m
Affected: Digital Wallets & Tokenization
Timeline · 2 updates
-
investigating Jan 27, 2026, 05:51 PM UTC
Marqeta engineers have been informed that Tokenmanager in the EU is experiencing an outage. Engineers are reverting a deployment that should restore full functionality shortly.
-
resolved Jan 27, 2026, 06:06 PM UTC
Engineers have confirmed the reverted deployment has restored functionality. Teams will continue working to understand the root cause of the degraded functionality.
Read the full incident report →
- Detected by Pingoru
- Jan 24, 2026, 07:43 AM UTC
- Resolved
- Jan 24, 2026, 03:20 PM UTC
- Duration
- 7h 36m
Affected: Reporting & Analytics
Timeline · 3 updates
-
identified Jan 24, 2026, 07:12 AM UTC
At 3 PM Pacific time on January 23rd the Marqeta clearing process experienced an errored condition. This error has been resolved and the clearing process has begun. Clearing files for our customers will be delayed up to 8 hours as a result of the error.
-
monitoring Jan 24, 2026, 07:43 AM UTC
Clearing processing is operating as expected as of 11:40 PM Pacific time. The earlier errored condition has created a backlog which is being processed at this time. Clearing files will be delivered as they are created and we expect all files to be delivered by 8 AM Pacific time Saturday, January 24th.
-
resolved Jan 24, 2026, 03:20 PM UTC
As of 7:15 AM Pacific time all Clearing Files have been processed and delivered.
Read the full incident report →
Critical January 22, 2026 - Detected by Pingoru
- Jan 22, 2026, 05:56 PM UTC
- Resolved
- Jan 22, 2026, 11:12 PM UTC
- Duration
- 5h 16m
Affected: Core APIACH ProcessingPayment ProcessingCard IssuingCard FulfillmentApplicationsCreditReporting & AnalyticsDigital Wallets & TokenizationRisk & Disputes3DS
Timeline · 11 updates
Read the full incident report →
- Detected by Pingoru
- Jan 19, 2026, 12:50 PM UTC
- Resolved
- Jan 19, 2026, 05:59 PM UTC
- Duration
- 5h 8m
Affected: 3DS
Timeline · 3 updates
-
identified Jan 19, 2026, 12:50 PM UTC
Cardholders may have experienced elevated authentication declines, increased processing latency, and failed 3DS card authentications since 12:04 PM GMT/7:04 AM EST. The issue is caused by a large amount of abnormal traffic generated by a bad merchant. Our engineering teams identified and isolated the traffic source, and are working towards potential improvements.
-
monitoring Jan 19, 2026, 01:19 PM UTC
The large spike in abnormal traffic has abated. We are still working to understand why this merchant sent so much traffic to us.
-
resolved Jan 19, 2026, 05:59 PM UTC
We have implemented mitigation steps and see no further recurrence of this incident since those changes were implemented.
Read the full incident report →