Update - 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.
May 05, 2026 - 14:12 PDT
Update - 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.
May 05, 2026 - 13:30 PDT
Update - 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.
May 05, 2026 - 12:30 PDT
Identified - 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.
May 05, 2026 - 11:30 PDT
Update - 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.
May 05, 2026 - 10:30 PDT
Update - 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.
May 05, 2026 - 09:32 PDT
Update - 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.
May 05, 2026 - 08:29 PDT
Update - 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.
May 05, 2026 - 07:29 PDT
Update - 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.
May 05, 2026 - 06:29 PDT
Investigating - An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST 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.
May 05, 2026 - 05:29 PDT
Core API Operational
ACH Processing Operational
Payment Processing Operational
Card Issuing Operational
Card Fulfillment Operational
Applications Operational
Credit Operational
Reporting & Analytics Partial Outage
Digital Wallets & Tokenization Operational
Risk & Disputes Operational
Webhooks Operational
Sandbox Operational
3DS Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
May 6, 2026

No incidents reported today.

May 5, 2026

Unresolved incident: Delay in Diva reports and MQD endpoints.

May 4, 2026

No incidents reported.

May 3, 2026

No incidents reported.

May 2, 2026

No incidents reported.

May 1, 2026

No incidents reported.

Apr 30, 2026
Resolved - This incident has been resolved. Service has been restored and customers should no longer experience any impact.
Apr 30, 10:34 PDT
Update - Engineers have confirmed that the incident is now stabilized. We will provide a final update once full resolution is confirmed
Apr 29, 15:20 PDT
Update - Work continues toward a full resolution. We will provide the next update when new information becomes available.
Apr 29, 14:15 PDT
Update - Our engineering teams remain focused on implementing the resolution. We will provide another update in approximately 60 minutes or when new information is provided.
Apr 29, 13:08 PDT
Identified - 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.
Apr 29, 12:04 PDT
Update - 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.
Apr 29, 11:35 PDT
Update - 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.
Apr 29, 11:04 PDT
Update - 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.
Apr 29, 10:32 PDT
Investigating - 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.
Apr 29, 10:04 PDT
Apr 29, 2026
Apr 28, 2026

No incidents reported.

Apr 27, 2026

No incidents reported.

Apr 26, 2026

No incidents reported.

Apr 25, 2026

No incidents reported.

Apr 24, 2026

No incidents reported.

Apr 23, 2026

No incidents reported.

Apr 22, 2026

No incidents reported.