- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Reporting & Analytics
- Down Index
- 35of 100
What to do
Check whether you use Marqeta Reporting & Analytics. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2d 12h it lasted.
Anything that failed between 2026-05-05 12:29 UTC and 2026-05-08 00:40 UTC may need a replay.Subscribe to Marqeta's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=marqeta works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Marqeta 11
- 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.
provider
- investigating
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.
provider
- investigating
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.
provider
- investigating
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.
provider
- investigating
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.
provider
- investigating
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.
provider
- 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.
provider
- 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.
provider
- 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 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.
provider
- identified
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.
provider
- resolved
All replicated assets in the system should now be fully synchronized.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-72164fd1b3
Is Marqeta still down?
No, this incident was resolved 2026-05-08 00:40 UTC. For Marqeta's live state, see https://down.guide/marqeta.
How long did it last?
2d 12h, from 2026-05-05 12:29 UTC to 2026-05-08 00:40 UTC, by the times Marqeta posted.
What was affected?
Marqeta named Reporting & Analytics.
What caused it?
Marqeta hasn't published a root cause. If it does, it shows here.
Where does this come from?
Marqeta's official status page, https://status.marqeta.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.