Marqeta Outage History

Started May 08, 2026, 12:46 AM UTC· resolved May 11, 2026, 10:57 PM UTC

1. investigating May 08, 2026, 12:46 AM UTC

   Marqeta engineers are detecting an elevated number of STIPs starting from about 4:30PM PST. Teams are monitoring an AWS us-east-1 outage as the likely cause. We will provide updates every 30 minutes or upon discovery of new information.

2. identified May 08, 2026, 01:14 AM UTC

   We are continuing to monitor the AWS problem in us-east-1, and we are seeing impact across many Marqeta services due to this. We are actively removing traffic from this region to limit the impact to our customers. Next update will be in 30 minutes or when AWS provides any additional context.

3. identified May 08, 2026, 01:45 AM UTC

   All Marqeta services remain impacted by the ongoing AWS us-east-1 outage with no ETA for resolution from AWS. The next update will be in 30 minutes or sooner if conditions change.

4. identified May 08, 2026, 02:14 AM UTC

   Marqeta services remain impacted by the ongoing AWS us-east-1 outage. AWS continues working to resolve increased temperatures in the affected availability zone with no current ETA for full resolution. Some services are beginning to see improvement. Next update in 30 minutes or sooner if conditions change.

5. identified May 08, 2026, 02:44 AM UTC

   Marqeta services remain impacted by the ongoing AWS us-east-1 outage. AWS continues working to resolve the thermal issue in the affected availability zone. We are closely monitoring their progress and our service recovery. Next update in 30 minutes or sooner if conditions change.

6. identified May 08, 2026, 03:14 AM UTC

   Marqeta services remain impacted by the ongoing AWS us-east-1 outage. AWS is shifting traffic away from the impacted zone for additional services. Our teams continue monitoring the situation closely and will provide the next update in 30 minutes or when new information is available.

7. identified May 08, 2026, 03:44 AM UTC

   Marqeta services remain impacted by the ongoing AWS us-east-1 outage. AWS is shifting traffic away from the impacted zone for additional services. Our teams continue monitoring the situation closely and will provide the next update in 30 minutes or when new information is available.

8. identified May 08, 2026, 04:14 AM UTC

   Marqeta services remain impacted by the ongoing AWS us-east-1 outage. AWS is shifting traffic away from the impacted zone for additional services. Our teams continue monitoring the situation closely and will provide the next update in 30 minutes or when new information is available.

9. identified May 08, 2026, 04:42 AM UTC

   Marqeta services remain impacted by the ongoing AWS us-east-1 outage. Our engineers are diligently monitoring the situation and implementing measures to reduce impact where possible. We will provide our next update when we receive additional information from AWS.

10. identified May 08, 2026, 05:29 AM UTC

    AWS is observing some early signs of recovery. Some of Marqeta services remain impacted by the ongoing AWS us-east-1 outage. Our engineers are diligently monitoring the situation and implementing measures to reduce impact where possible. We will provide our next update when we receive additional information from AWS.

11. monitoring May 08, 2026, 06:53 AM UTC

    We are continuing to observe improvements to Marqeta's services. Engineers are continuing to put mitigations in place, such as moving traffic away from the affected region and availability zone. We will also continue monitoring the situation overnight for any changes in status. Our next update will be at 10:00 EST.

12. monitoring May 08, 2026, 02:00 PM UTC

    We are continuing to observe improvements to Marqeta's services. Engineers are continuing to put mitigations in place, such as moving traffic away from the affected region and availability zone. We will continue monitoring the situation throughout the day for any changes in status. We will provide our next update when we receive additional information from AWS.

13. monitoring May 08, 2026, 09:46 PM UTC

    Nearly all Marqeta services are now fully operational. Engineers are continuing to mitigate some data discrepancies in certain services. We will continue monitoring the situation throughout the weekend. We will provide our next update Monday the 11th at 10:00 am EST, or if we become aware of a substantial change in condition.

14. monitoring May 11, 2026, 02:09 PM UTC

    Nearly all Marqeta services are now fully operational. Engineers are continuing to mitigate some data discrepancies in certain services. We will provide our next update when the data has been fully remediated, or if we become aware of a substantial change in condition.

15. resolved May 11, 2026, 10:57 PM UTC

    All of Marqeta's services should now be fully operational.

Read the full incident report →

Started May 05, 2026, 12:29 PM UTC· resolved May 08, 2026, 12:40 AM UTC

1. investigating May 05, 2026, 12:29 PM UTC

   An external vendor's unexpected cluster maintenance starting from about 4:00 PM on May 4th is causing a severe lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams are engaging with the external vendor to resolve the upstream cluster issue, running checks to quantify the data lag load times, and ensuring internal pipelines are ready to automatically process all delayed data once restored. We will have more information about an ETA to restoration once the external vendor provides their own ETA. Our next update will be in 60 minutes.

2. investigating May 05, 2026, 01:29 PM UTC

   An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have escalated our engagement with the external vendor to resolve quicker. We will have more information about an ETA to restoration once the external vendor provides their own ETA. Our next update will be in 60 minutes.

3. investigating May 05, 2026, 02:29 PM UTC

   An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have escalated our engagement with the external vendor to resolve quicker. We will have more information about an ETA to restoration once the external vendor provides their own ETA. Our next update will be in 60 minutes.

4. investigating May 05, 2026, 03:29 PM UTC

   An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have escalated our engagement with the external vendor to resolve quicker. We will have more information about an ETA to restoration once the external vendor provides their own ETA. Our next update will be in 60 minutes.

5. investigating May 05, 2026, 04:32 PM UTC

   An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have escalated our engagement with the external vendor to resolve quicker. We will have more information about an ETA to restoration once the external vendor provides their own ETA. Our next update will be in 60 minutes.

6. investigating May 05, 2026, 05:30 PM UTC

   An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have escalated our engagement with the external vendor to resolve quicker. We will have more information about an ETA to restoration once the external vendor provides their own ETA. Our next update will be in 60 minutes.

7. identified May 05, 2026, 06:30 PM UTC

   An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have observed assets beginning to catch up. We are continuing our engagement with the external vendor to resolve quicker and receive an ETA for full restoration. Our next update will be in 60 minutes.

8. identified May 05, 2026, 07:30 PM UTC

   An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have observed assets beginning to catch up. We are continuing our engagement with the external vendor to resolve quicker and receive an ETA for full restoration. Our next update will be in 60 minutes.

9. identified May 05, 2026, 08:30 PM UTC

   An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have observed assets continuing to improve. Some corrected reports will be available in the early morning of May 6th. We are continuing our engagement with the external vendor to resolve quicker and receive an ETA for full restoration. Our next update will be in 60 minutes.

10. identified May 05, 2026, 09:12 PM UTC

    An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is impacting data replication for transactional data in Diva reports and MQD endpoints. All replicated assets in the system are now fully synchronized with the exception of one cluster, which currently shows approximately 8 hours behind and is progressing toward full synchronization. Marqeta teams continue to monitor the recovery process and maintain engagement with the external vendor. More detailed information will be provided tomorrow morning, or if new information becomes available.

11. resolved May 08, 2026, 12:40 AM UTC

    All replicated assets in the system should now be fully synchronized.

Read the full incident report →

Started Apr 29, 2026, 05:04 PM UTC· resolved Apr 30, 2026, 05:34 PM UTC

1. investigating Apr 29, 2026, 05:04 PM UTC

   Starting at 13:00 EST, 3DS is experiencing degraded performance that may cause challenge timeouts. Our engineering team is investigating the root cause. We will provide another update in approximately 30 minutes.

2. investigating Apr 29, 2026, 05:32 PM UTC

   3DS is experiencing degraded performance that may cause challenge timeouts and STIPs. Our engineering team is investigating the root cause. Next update will be in approximately 30 minutes or when new information becomes available.

3. investigating Apr 29, 2026, 06:04 PM UTC

   Our engineering team is actively continuing to investigate the root cause of the 3DS performance issue. Challenge timeouts and STIPs may still be impacting customers. We remain focused on resolution and will provide another update in approximately 30 minutes.

4. investigating Apr 29, 2026, 06:35 PM UTC

   Multiple teams are working together to investigate and resolve the 3DS performance degradation. Challenge timeouts and STIPs may continue to impact customers. We will provide another update in approximately 30 minutes.

5. identified Apr 29, 2026, 07:04 PM UTC

   Engineers have identified the root cause and are now working on a resolution. We will provide another update in approximately 60 minutes or when new information becomes available.

6. identified Apr 29, 2026, 08:08 PM UTC

   Our engineering teams remain focused on implementing the resolution. We will provide another update in approximately 60 minutes or when new information is provided.

7. identified Apr 29, 2026, 09:15 PM UTC

   Work continues toward a full resolution. We will provide the next update when new information becomes available.

8. identified Apr 29, 2026, 10:20 PM UTC

   Engineers have confirmed that the incident is now stabilized. We will provide a final update once full resolution is confirmed

9. resolved Apr 30, 2026, 05:34 PM UTC

   This incident has been resolved. Service has been restored and customers should no longer experience any impact.

Read the full incident report →

Started Apr 03, 2026, 07:44 PM UTC· resolved Apr 04, 2026, 04:15 AM UTC

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

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

3. resolved Apr 04, 2026, 04:15 AM UTC

   Engineers have resolved the last known instances of this issue.

Read the full incident report →

Started Apr 02, 2026, 08:31 PM UTC· resolved Apr 06, 2026, 06:32 PM UTC

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

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

3. 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 →

Started Mar 17, 2026, 04:09 PM UTC· resolved Mar 17, 2026, 07:27 PM UTC

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

2. 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 →

Started Mar 12, 2026, 08:29 PM UTC· resolved Mar 13, 2026, 12:50 AM UTC

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

2. 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 →

Started Mar 03, 2026, 04:16 PM UTC· resolved Mar 04, 2026, 05:05 PM UTC

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

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

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

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

5. 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 →

Started Feb 25, 2026, 06:07 PM UTC· resolved Feb 25, 2026, 06:07 PM UTC

1. 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 →

Started Feb 13, 2026, 01:15 AM UTC· resolved Feb 13, 2026, 02:35 PM UTC

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

2. 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 →

Started Feb 11, 2026, 09:51 AM UTC· resolved Feb 11, 2026, 02:21 PM UTC

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

2. resolved Feb 11, 2026, 02:21 PM UTC

   This has now been resolved.

Read the full incident report →

Started Feb 06, 2026, 08:45 PM UTC· resolved Feb 13, 2026, 10:25 PM UTC

1. investigating Feb 06, 2026, 08:45 PM UTC

   Starting January 22nd, some customers may notice duplicate transaction postings. Our engineering team is actively working to resolve this issue. Affected customers do not need to take any action.

2. investigating Feb 06, 2026, 11:16 PM UTC

   Our team is conducting a thorough investigation to determine the root cause while working on a resolution. We will provide updates as soon as new information becomes available.

3. identified Feb 07, 2026, 12:00 AM UTC

   We've identified the cause of the duplicate transaction issue and are implementing a fix.

4. identified Feb 07, 2026, 02:05 AM UTC

   Our team has identified the cause of duplicate transaction postings as an issue introduced in a recent release. We've successfully completed a rollback for Mastercard. As a precautionary measure, we're scheduling the Visa and Pulse fixes for Monday, February 9th to avoid any potential impact during the weekend. All duplicate transactions will be automatically reversed within 48 hours, and no action is required from affected customers. We will provide our next update on Monday unless new information becomes available sooner.

5. identified Feb 09, 2026, 09:41 PM UTC

   Engineers are scheduling the fix for Visa and Pulse. No duplicate transactions have been observed since Friday, February 6th at 6:00 PM PT/2:00 AM UTC. We do not expect any further impact to either card network.

6. identified Feb 10, 2026, 08:32 PM UTC

   A non-impact partial fix for the issue was applied to Pulse on February 9th at 06:30 PM PT. Our engineering team is currently working with priority on finalizing the full-scale fix, and we will provide an update as soon as it is ready for deployment. We continue to confirm that no duplicate transactions have been observed since Friday, February 6th at 6:00 PM PT/2:00 AM UTC. We do not expect any further impact to either the Visa or Pulse card networks. We deeply appreciate your patience and remain fully committed to providing explicit communication throughout the resolution process.

7. identified Feb 11, 2026, 05:34 PM UTC

   The full rollback for Visa was successfully completed in close coordination with the Visa team on February 10th at 9:30 PM PT, The implementation was executed smoothly, and no abnormality was observed. For Pulse, we are actively coordinating next steps with their team. For an aligned maintenance window for fix implementation to ensure proper timing and minimize any potential downtime. We continue to closely monitor the environment and confirm that no duplicate transactions have been observed since Friday, February 6th at 6:00 PM PT / 2:00 AM UTC. At this time, we do not anticipate additional impact to either the Visa or Pulse card networks. We will provide further updates as additional information becomes available and appreciate your continued patience.

8. resolved Feb 13, 2026, 10:25 PM UTC

   The full fix has now been successfully implemented across all Pulse routers as of February 13th approximately 2:15 PM PT. This follows the previously completed Visa rollback on February 10th, and the fix is now fully generalized across all networks. The implementation was executed in coordination with our network partners and completed as planned. We continue to closely monitor the environment and confirm that no duplicate transactions have been observed since Friday, February 6th at 6:00 PM PT / 2:00 AM UTC. The system remains stable, and no additional impact is anticipated to card networks. We appreciate your patience throughout this process.

Read the full incident report →

Started Jan 27, 2026, 05:51 PM UTC· resolved Jan 27, 2026, 06:06 PM UTC

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

2. 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 →

Started Jan 24, 2026, 07:43 AM UTC· resolved Jan 24, 2026, 03:20 PM UTC

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

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

3. 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 →

Started Jan 22, 2026, 05:56 PM UTC· resolved Jan 22, 2026, 11:12 PM UTC

1. investigating Jan 22, 2026, 05:56 PM UTC

   We have identified multiple outages across multiple services. Marqeta engineers are working hard to assess the scope of the outage, determine root cause, and provide timelines for restoration. Next update will be at 10:15 PST

2. investigating Jan 22, 2026, 06:14 PM UTC

   Marqeta is seeing multiple services impacted. We have multiple teams engaged and triaging. We do not yet have root cause. We will update next at 10:30 PST.

3. investigating Jan 22, 2026, 06:30 PM UTC

   Marqeta is seeing multiple services impacted. We have multiple teams engaged and triaging. The team has isolated root cause to a networking configuration issue. We will update next at 10:45 PST.

4. investigating Jan 22, 2026, 06:45 PM UTC

   Marqeta is seeing multiple services impacted. We have multiple teams engaged and triaging. The team has isolated root cause to a networking configuration issue. We are evaluating resolution paths presently, but do not yet have an ETA for restoration. We will update next at 11:00 PST.

5. investigating Jan 22, 2026, 07:00 PM UTC

   Marqeta is seeing multiple services impacted. We have multiple teams engaged and triaging. The team has isolated root cause to a networking configuration issue. We are evaluating resolution paths presently, but do not yet have an ETA for restoration. We will update next at 11:15 PST.

6. identified Jan 22, 2026, 07:15 PM UTC

   Marqeta is seeing multiple services impacted. This will include 500-level API errors, Tokenization Failures, Payment Processing Delays, Dashboard and Reporting Issues, KYC and Customer Onboarding, and Webhooks Functionality. We have multiple teams engaged and triaging. The team has isolated root cause to a networking configuration issue. A fix has been deployed and we are seeing signs of recovery. We will be able to provide an ETA for full restoration once we are confident the recovery is holding. We will update next at 11:30 PST or as soon as restoration is confirmed.

7. identified Jan 22, 2026, 07:30 PM UTC

   Marqeta is seeing multiple services impacted. This will include 500-level API errors, Tokenization Failures, Payment Processing Delays, Dashboard and Reporting Issues, KYC and Customer Onboarding, and Webhooks Functionality. The team has isolated root cause to a networking configuration issue. A fix has been deployed and we are seeing services recovering. We will be able to provide an ETA for full restoration once we are confident the recovery is holding across all services. We will update next at 11:45 PST or as soon as restoration is confirmed.

8. identified Jan 22, 2026, 07:45 PM UTC

   Marqeta is seeing multiple services impacted. This will include 500-level API errors, Tokenization Failures, Payment Processing Delays, Dashboard and Reporting Issues, KYC and Customer Onboarding, and Webhooks Functionality. The team has isolated root cause to a networking configuration issue. A fix has been deployed and we are seeing services recovering. The teams are isolating and addressing any subsequent effects of the outage. We will be able to provide an ETA for full restoration once we are confident the recovery is holding across all services. We will update next at 12:15 PST or as soon as restoration is confirmed.

9. identified Jan 22, 2026, 08:15 PM UTC

   Marqeta is seeing multiple services impacted. This will include 500-level API errors, Tokenization Failures, Payment Processing Delays, Dashboard and Reporting Issues, KYC and Customer Onboarding, and Webhooks Functionality. The team has isolated root cause to a networking configuration issue. A fix has been deployed and most services have recovered. The teams are isolating and addressing any subsequent effects of the outage. We will be able to provide an ETA for full restoration once we are confident the recovery is holding across all services and all subsequent effects are known and addressed. We will update next as soon as restoration is confirmed.

10. monitoring Jan 22, 2026, 08:27 PM UTC

    The team has isolated root cause to a networking configuration issue. A fix has been deployed and services have recovered. The teams are continuing to isolate and address any lingering effects of the outage. Further updates will be provided here as they are determined.

11. resolved Jan 22, 2026, 11:12 PM UTC

    Marqeta experienced an outage today affecting multiple services. Once the team isolated the root cause to a networking configuration issue, a fix was deployed and all impacted services were fully restored. The recovery is holding across all services. If you have any questions related to this matter, please reach out to [email protected].

Read the full incident report →

Started Jan 19, 2026, 12:50 PM UTC· resolved Jan 19, 2026, 05:59 PM UTC

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

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

3. 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 →

Started Jan 06, 2026, 10:46 AM UTC· resolved Jan 07, 2026, 10:01 AM UTC

1. identified Jan 06, 2026, 10:46 AM UTC

   Some clearing transactions are delayed due to a corrupted file from Visa containing malformed characters. We've notified Visa and are waiting for a corrected file. Affected clearings will be processed once received. We will update here once Visa send a corrected file. We have no ETA as yet from Visa for this.

2. identified Jan 06, 2026, 02:20 PM UTC

   Visa has escalated the issue to their Clearing team for investigation. Once their investigation in complete they will be able to provide us with an corrected file. Affected clearings will be processed once received. We will update here once Visa send a corrected file. We have no ETA as yet from Visa for this.

3. identified Jan 06, 2026, 05:44 PM UTC

   We are continuing to wait for Visa's Clearing team to provide updates. In the meantime, Marqeta engineers are investigating the possibility of repairing Visa's corrupted file. We will update here once Visa sends a corrected file. We have no ETA as yet from Visa for this. We will also update here if the file repair approach is possible.

4. identified Jan 06, 2026, 07:45 PM UTC

   Marqeta engineers have determined that Visa's corrupted file may not be possible to repair. We are continuing to wait for Visa's Clearing team to provide updates. We will update here once Visa sends a corrected file. We have no ETA as yet from Visa for this.

5. identified Jan 06, 2026, 11:45 PM UTC

   The corrupted Visa file has been repaired and is now processing. Reporting should be completed shortly. We do not yet have an ETA for when transactions will be cleared, one will be shared here once it has been determined.

6. resolved Jan 07, 2026, 10:01 AM UTC

   All clearings have been posted from the affected file. If you notice any discrepancies, please raised them with Marqeta support.

Read the full incident report →

Started Dec 16, 2025, 10:51 AM UTC· resolved Dec 19, 2025, 12:51 AM UTC

1. investigating Dec 16, 2025, 10:51 AM UTC

   We are investigating issues processing Visa clearing and settlement files for today. We see no issues with clearings and settlement files for other networks. We see no impact to authorizations from any Network. Since the files have not been processed, impacted Marqeta customers on Visa will see an absence of clearing webhooks, and no Visa VSS report files until this incident is resolved. Prrefunded customers will see no clearings posted to cardholder balances until this incident is mitigated.

2. investigating Dec 16, 2025, 11:17 AM UTC

   Engineers found the root cause, and have mitigated. The files are now being processed, Marqeta customers will start to see clearing webhooks now. We will monitor the procesing of clearing files, and update this incident when we are caught up, and will note that we are Operational then.

3. investigating Dec 17, 2025, 04:20 PM UTC

   Engineers have clarified that Mastercard files were also impacted in the same timeframe. We are continuing to monitor the processing of Visa and Mastercard clearing files. Currently, the engineers have re-created the program level split files for clearing and reporting. As a part of this work there is a focus on preventing duplicate files from being sent. Once complete, we will send the split files to be cleared and/or delivered to customers. The next update will occur when we have confirmed that all files are caught up.

4. investigating Dec 18, 2025, 01:36 AM UTC

   Visa files have finished processing. Engineers have completed the program level split files and they are now currently processing; we will continue to monitor their progress. While we don't have an exact ETA for complete resolution at this time, we will provide additional details as they become available. The next update will occur when all files have been fully processed and we can confirm operational status.

5. investigating Dec 18, 2025, 04:57 PM UTC

   For Mastercard, program level split files are continuing to progress with no ETA yet. Clearing webhooks have an ETA of one hour. Engineers are investigating reports of missing Mastercard T112 reports, and will look to resend them by end of day. While we don't have an exact ETA for complete resolution at this time, we will continue to provide additional details as they become available.

6. resolved Dec 19, 2025, 12:51 AM UTC

   As of 4:40 PM PT, engineers confirmed that all files have completed processing. Clearing webhooks and reporting should be functioning as expected.

Read the full incident report →

Started Nov 13, 2025, 07:55 PM UTC· resolved Nov 14, 2025, 01:16 AM UTC

1. investigating Nov 13, 2025, 07:55 PM UTC

   Marqeta has identified an issue that is impacting Risk & Dispute services we provide. We are actively working to resolve the issue as quickly as possible

2. identified Nov 13, 2025, 08:19 PM UTC

   Marqeta engineers are preparing a temporary hot fix to mitigate the impact on our customers, and investigations are ongoing to isolate the issue permanently.

3. identified Nov 13, 2025, 09:24 PM UTC

   Marqeta Engineers are sill developing a fix to mitigate the impact on our customers with priority, and service status updates will be shared once available

4. monitoring Nov 13, 2025, 10:25 PM UTC

   At 13:20 PT, Marqeta's team deployed a hot fix to mitigate the impact and solve the issue with Dispute services ,and post deployment service verification showed steady gradual rebound along with multiple service verifications with our customers. Engineering teams are still engaged for service close monitoring tell end of business day.

5. resolved Nov 14, 2025, 01:16 AM UTC

   After close monitoring, engineers have confirmed that the issue is now stable. Services should be functioning as expected.

Read the full incident report →

Started Nov 12, 2025, 03:35 PM UTC· resolved Nov 14, 2025, 04:13 PM UTC

1. investigating Nov 12, 2025, 03:35 PM UTC

   On Nov 11, Marqeta observed a technical issue that is disturbing the communication of some of the clearing & settlement files on Visa Network. Our teams are actively investigating to mitigate the impact and resolve the issue.

2. identified Nov 12, 2025, 06:03 PM UTC

   Issue was identified to be an internal service traffic issue that is impacting some of the file processing on Visa network, and Engineering team is currently working on developing a fix to address the reporting and clearing services issue. In the mean time, we are processing existing visa network files at reduced capacity.

3. identified Nov 12, 2025, 07:32 PM UTC

   Engineers have confirmed that Pulse files are also affected. Engineers are continuing to actively investigate to mitigate the impact and resolve the issue.

4. identified Nov 12, 2025, 08:36 PM UTC

   Engineers are continuing to work to restore file processing. They anticipate this will be resolved today. Additional updates and time frames will be provided here once they are known.

5. identified Nov 12, 2025, 10:39 PM UTC

   Engineering teams continue efforts to restore file processing capabilities. Additional updates and timelines to be communicated as they become available.

6. identified Nov 13, 2025, 01:12 AM UTC

   Engineering teams are actively working to restore file processing. We will continue to share updates and new information as it becomes available.

7. identified Nov 13, 2025, 04:11 AM UTC

   We are continuing to work on a fix for this issue. Full resolution is expected tomorrow morning.

8. identified Nov 13, 2025, 03:22 PM UTC

   We are continuing to work on a fix for this issue. Full resolution is expected today.

9. identified Nov 13, 2025, 04:42 PM UTC

   Engineers have resolved the root cause affecting the processing of Visa and Pulse clearing and reports. Visa reports are processed and delivery should be caught up for all customers. For Pulse the reports from before November 13th have been delivered. Pulse reports from today are still processing. These files will be processed and delivered today. For clearing on Visa, we are still working through the backlog of the files before November 13th. We expect this to be caught up today.

10. identified Nov 13, 2025, 05:49 PM UTC

    Visa reports are processed and delivery should be caught up for all customers. For Pulse the reports from before November 13th have been delivered. Pulse reports from today are still processing. These files will be processed and delivered today. For clearing on Visa, we are still working through the backlog of the files before November 13th. We expect this to be caught up today.

11. identified Nov 13, 2025, 06:50 PM UTC

    Pulse reports from today should be delivered for all customers. The Visa clearing is continuing to process. We now expect this to be caught up by tomorrow morning.

12. resolved Nov 14, 2025, 04:13 PM UTC

    Visa and Pulse reports should now be caught up for all customers. Visa clearing should now be caught up for all customers.

Read the full incident report →

Started Nov 07, 2025, 10:59 PM UTC· resolved Nov 08, 2025, 12:32 AM UTC

1. identified Nov 07, 2025, 10:59 PM UTC

   There has been a delay in the delivery of Visa SMS and VSS Detail files today. The delay was caused by a recent system change that is preventing the reports from being delivered to the designated SFTP location. We are rolling back the change to remediate the situation.

2. resolved Nov 08, 2025, 12:32 AM UTC

   We have confirmed that all files have been processed and delivered.

Read the full incident report →

Started Oct 28, 2025, 04:16 PM UTC· resolved Oct 28, 2025, 07:31 PM UTC

1. investigating Oct 28, 2025, 04:16 PM UTC

   Some customers may find some features of Marqeta Dashboard report customization are unavailable. This will include program filtering. Engineers are aware and are working on restoring all features.

2. resolved Oct 28, 2025, 07:31 PM UTC

   Engineers have confirmed that the program selector should be working as intended.

Read the full incident report →

Started Oct 21, 2025, 12:40 PM UTC· resolved Oct 22, 2025, 01:58 PM UTC

1. identified Oct 21, 2025, 12:40 PM UTC

   Bank files data for October 20th is incomplete as a consequence of AWS outage, causing a delay for bank files for that day. MQD/DIVA API data is also incomplete. Our Engineering is working on further recovery and the files will be delivered when data is complete and included in the reports.

2. monitoring Oct 22, 2025, 01:30 PM UTC

   MQD / DIVA API reports are now refreshed and up to date for the October 20th data.

3. resolved Oct 22, 2025, 01:58 PM UTC

   Bank files and MQD / DIVA API reports are now refreshed and up to date for the October 20th data.

Read the full incident report →

Started Oct 20, 2025, 08:02 AM UTC· resolved Oct 21, 2025, 11:13 AM UTC

1. investigating Oct 20, 2025, 08:02 AM UTC

   Marqeta engineers are tracking a possible aws-us-east-1 outage that is affecting multiple systems and other services. This can include SMS, tokenization, and more. Investigation is underway and more information will be available soon.

2. investigating Oct 20, 2025, 08:12 AM UTC

   Marqeta engineers are tracking a confirmed aws-us-east-1 outage that is affecting multiple systems and other services. This can include SMS, Tokenization, KYC, APIs, Marqeta Dashboard, and more. Investigation is underway and more information will be available soon.

3. identified Oct 20, 2025, 09:06 AM UTC

   Marqeta engineers are tracking a confirmed AWS us-east-1 outage that is affecting multiple systems and other services. This can include SMS, Tokenization, KYC, APIs, Marqeta Dashboard, and more. Investigation is continuing to understand the scope of impacted systems. We are monitoring AWS communication channels for updates.

4. monitoring Oct 20, 2025, 09:52 AM UTC

   AWS reports they are seeing significant signs of recovery. We are monitoring this recovery and the recovery of Marqeta services.

5. monitoring Oct 20, 2025, 10:53 AM UTC

   AWS reports they are seeing significant signs of recovery. We are monitoring this recovery and the recovery of Marqeta services.

6. monitoring Oct 20, 2025, 11:10 AM UTC

   AWS reports they are seeing significant signs of recovery. AWS Fargate is still affected, which directly impacts all webhooks. Engineers are continuing to remediate and will slowly resume webhooks services once AWS has recovered.

7. monitoring Oct 20, 2025, 12:21 PM UTC

   AWS Fargate is still affected, which directly impacts all webhooks. AWS reports working through processing the backlog of SQS messages in Lambda queues. Engineers are continuing to monitor and will slowly resume webhooks services once AWS has recovered.

8. monitoring Oct 20, 2025, 01:29 PM UTC

   AWS Fargate is still affected, which directly impacts all webhooks. AWS reports they are continuing to work through processing the backlog of SQS messages in Lambda queues. Engineers are continuing to monitor and will slowly resume webhooks services once AWS has recovered.

9. monitoring Oct 20, 2025, 01:51 PM UTC

   Numerous AWS services are still affected, which directly impacts all webhooks. Marqeta engineers have also confirmed this will delay all bank files and all DIVA MQD reports. Additionally, recon and settlement reports are delayed. AWS reports they are still experiencing elevated errors for new EC2 instance launches. Engineers are continuing to monitor and will be able to slowly resume webhooks services and reporting once AWS has recovered.

10. monitoring Oct 20, 2025, 02:10 PM UTC

    Numerous AWS services are still degraded. This directly impacts several Marqeta services, including: Delayed or unsent webhooks; Delay in all bank files and all DIVA MQD reports; Delay in recon and settlement reports; Delay in API responses; Delay in VAU and ABU reports; Delay in some direct deposits; Partial outage to KYC Services; Degraded performance in tokenization functions. AWS reports they are still experiencing elevated errors for new EC2 instance launches. They have not yet provided an ETA to partial or complete restoration, but are making periodic status updates. Engineers are continuing to monitor and will be able to resume affected services and reporting once AWS has recovered.

11. monitoring Oct 20, 2025, 03:22 PM UTC

    Numerous AWS services are still degraded. This directly impacts several Marqeta services, including: Delayed or unsent webhooks; Delay in all bank files and all DIVA MQD reports; Delay in recon and settlement reports; Delay in API responses; Delay in VAU and ABU reports; Delay in some direct deposits; Delay in fulfillment files; Partial outage to KYC Services; Degraded Network Updates service; Degraded performance in tokenization functions. AWS reports they are continuing to investigate the root cause for the network connectivity issues that are impacting AWS services. They have not yet provided an ETA to partial or complete restoration, but are making periodic status updates. Engineers are continuing to monitor and will be able to resume affected services and reporting once AWS has recovered.

12. monitoring Oct 20, 2025, 04:19 PM UTC

    Numerous AWS services are still degraded. This directly impacts several Marqeta services, including: Delayed or unsent webhooks; Delay in all bank files and all DIVA MQD reports; Delay in recon and settlement reports; Delay in API responses; Delay in VAU and ABU reports; Delay in some direct deposits; Delay in fulfillment files; Partial outage to KYC Services; Degraded Network Updates service; Degraded performance in tokenization functions. AWS reports they are continuing to investigate the root cause for the network connectivity issues that are impacting AWS services. They have not yet provided an ETA to partial or complete restoration, but are making periodic status updates. Engineers are continuing to monitor and will be able to resume affected services and reporting once AWS has recovered.

13. monitoring Oct 20, 2025, 05:35 PM UTC

    Numerous AWS services are still degraded. This directly impacts several Marqeta services, including: Delayed or unsent webhooks; Delay in all bank files and all DIVA MQD reports; Delay in recon and settlement reports; Delay in API responses; Delay in VAU and ABU reports; Delay in some direct deposits; Delay in fulfillment files; Partial outage to KYC Services; Degraded Network Updates service; Degraded performance in tokenization functions. AWS reports they are continuing to investigate the root cause for the network connectivity issues that are impacting AWS services. They have not yet provided an ETA to partial or complete restoration, but are making periodic status updates. Engineers are continuing to monitor and will be able to resume affected services and reporting once AWS has recovered.

14. monitoring Oct 20, 2025, 06:35 PM UTC

    Numerous AWS services are still degraded. This directly impacts several Marqeta services, including: Delayed or unsent webhooks; Delay in all bank files and all DIVA MQD reports; Delay in recon and settlement reports; Delay in API responses; Delay in VAU and ABU reports; Delay in some direct deposits; Delay in fulfillment files; Partial outage to KYC Services; Degraded Network Updates service; Degraded performance in tokenization functions. AWS reports they are continuing working on mitigating the issue and investigating the root cause for the network connectivity issues that are impacting AWS services. No ETA provided yet from AWS side for full service restoration. Engineers are continuing to monitor and will be able to resume affected services and reporting once AWS has recovered.

15. monitoring Oct 20, 2025, 06:41 PM UTC

    We are continuing to monitor for any further issues.

16. monitoring Oct 20, 2025, 07:34 PM UTC

    Numerous AWS services are still degraded. This directly impacts several Marqeta services, including: Delayed or unsent webhooks; Delay in all bank files and all DIVA MQD reports; Delay in recon and settlement reports; Delay in API responses; Delay in VAU and ABU reports; Delay in some direct deposits; Delay in fulfillment files; Partial outage to KYC Services; Degraded Network Updates service; Degraded performance in tokenization functions. AWS reports they are continuing working on mitigating the issue and investigating the root cause for the network connectivity issues that are impacting AWS services. No ETA provided yet from AWS side for full service restoration. Engineers are continuing to monitor and will be able to resume affected services and reporting once AWS has fully recovered.

17. monitoring Oct 20, 2025, 08:35 PM UTC

    Numerous AWS services are degraded. This directly impacts several Marqeta services, including: Impacted services : Delayed or unsent webhooks; Delay in all bank files and all DIVA MQD reports; Delay in recon and settlement reports; Delay in API responses; Delay in VAU and ABU reports; Delay in some direct deposits; Delay in fulfillment files; Partial outage to KYC Services; Degraded 3DS service; Degraded performance in tokenization functions. Degraded Sandbox service; Recovered /improved services : Network Updates service (Recovered). AWS reports they are continuing working on mitigating the issue and investigating the root cause for the network connectivity issues that are impacting AWS services. No ETA provided yet from AWS side for full service restoration. Engineers are continuing to monitor and will be able to resume affected services and reporting once AWS has fully recovered.

18. monitoring Oct 20, 2025, 09:34 PM UTC

    Numerous AWS services are degraded. This directly impacts several Marqeta services, including: Impacted services : Delay in all bank files and all DIVA MQD reports; Delay in recon and settlement reports; Delay in VAU and ABU reports; Delay in some direct deposits; Delay in fulfillment files; Partial outage to KYC Services; Degraded 3DS service; Degraded Sandbox service; Delay in webhooks; Recovered services : Network Updates service Tokenization services Core API response AWS reports they are continuing working on mitigating the issue and investigating the root cause for the network connectivity issues that are impacting AWS services. Engineers are continuing to monitor and will be able to resume affected services and reporting once AWS has fully recovered.

19. monitoring Oct 21, 2025, 01:22 AM UTC

    At 15:01 PT, AWS confirmed that service restoration from their side after network connectivity issues they had across US-EAST-1 Regions was resolved. However, some AWS services are still degraded due to AWS's backlog of messages that will take a few hours to be processed, and an RCA will be shared from AWS side. All of Marqeta’s impacted services have been restored. For Webhooks service, processing was disrupted starting at approximately 12:00 AM PT. We have since restored service as of 12:30 PM PT, and we began flushing the queued webhooks starting at 6:15 PM PT, with processing expected to complete within 12 hours. We are actively monitoring systems closely to ensure continued stability.

20. resolved Oct 21, 2025, 11:13 AM UTC

    As of 12:30am PT, 7:30am GMT today, all historic webhooks have been cleared from the queues.

Read the full incident report →

Started Oct 16, 2025, 09:34 PM UTC· resolved Oct 16, 2025, 09:34 PM UTC

1. resolved Oct 16, 2025, 09:34 PM UTC

   Some EU customers may have experienced downtime between 20:25:30 - 20:43:30 UTC on October 16th due to a maintenance task.

Read the full incident report →