Marqeta incident

MQD and Diva Access issue

Critical Resolved View vendor source →

Marqeta experienced a critical incident on July 31, 2026 affecting Reporting & Analytics and 3DS, lasting 1h 18m. The incident has been resolved; the full update timeline is below.

Started
Jul 31, 2026, 05:19 PM UTC
Resolved
Jul 31, 2026, 06:38 PM UTC
Duration
1h 18m
Detected by Pingoru
Jul 31, 2026, 05:19 PM UTC

Affected components

Reporting & Analytics3DS

Update timeline

  1. investigating Jul 31, 2026, 05:19 PM UTC

    Marqeta engineering team is investigating a service disruption affecting the Marqeta Dashboard and Diva. Our teams are actively working to mitigate the issue and restore full service.A follow-up notification with more detail will be sent within 30 minutes.

  2. investigating Jul 31, 2026, 05:47 PM UTC

    Marqeta engineering is actively investigating a service disruption affecting database connectivity across multiple services, including the Marqeta Dashboard, Diva, and 3DS. Our teams are currently investigating underlying infrastructure and network-level issues. We have escalated the matter to service provider and are coordinating across engineering teams to restore service. Further updates will be provided as our investigation progresses.

  3. identified Jul 31, 2026, 06:04 PM UTC

    Our engineering team has identified the root cause of the service disruption affecting the Marqeta Dashboard, Diva, and 3DS. The issue originated from an infrastructure configuration that inadvertently restricted network connectivity for our production database environment. We are currently implementing a fix to restore the service . We apologize for the impact this has caused and will provide further updates as our restoration efforts conclude.

  4. resolved Jul 31, 2026, 06:38 PM UTC

    Marqeta engineering teams have resolved the service disruption affecting the Marqeta Dashboard, Diva, and 3DS at 11:00 PDT. The root cause was an infrastructure configuration change that inadvertently restricted network connectivity for our production database environment, which has since been remediated. We have concluded performance monitoring to ensure long-term stability, and all services are now operational. We appreciate your patience as we worked to resolve this incident.