Marqeta Outage History

Marqeta is up right now

There were 10 Marqeta outages since February 6, 2026 totaling 346h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.marqeta.com

Minor April 29, 2026

3DS Service Degradation

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

Minor April 3, 2026

Increase Rate Of Magstripe Declines

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

Minor April 2, 2026

Intermittent STIPs across multiple networks

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

Minor March 17, 2026

Delay in bank file delivery

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

Notice March 12, 2026

STIPS on Master Card network

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

Minor March 3, 2026

FEDACH Processing Delay

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

Notice February 25, 2026

Marqeta Dashboard Login Outage

Detected by Pingoru
Feb 25, 2026, 06:07 PM UTC
Resolved
Feb 25, 2026, 06:07 PM UTC
Duration
Timeline · 1 update
  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 →

Notice February 13, 2026

Elevated API Timeouts

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

Minor February 11, 2026

Sandbox simulations/cardtransactions/ endpoint is reporting 503

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

Notice February 6, 2026

Duplicate transaction postings

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

Looking to track Marqeta downtime and outages?

Pingoru polls Marqeta's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Marqeta reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Marqeta alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Marqeta for free

5 free monitors · No credit card required