Bitvavo incident

Technical Difficulties Affecting FIX API

Minor Resolved View vendor source →

Bitvavo experienced a minor incident on August 21, 2026 affecting API, lasting —. The incident has been resolved; the full update timeline is below.

Started
Aug 21, 2026, 07:47 AM UTC
Resolved
Aug 21, 2026, 07:47 AM UTC
Duration
—
Detected by Pingoru
Aug 21, 2026, 07:47 AM UTC

Affected components

API

Update timeline

  1. investigating Aug 15, 2026, 05:30 AM UTC

    Status: Investigating We are investigating an issue affecting the FIX API on our platform. Users may experience degraded performance or failed FIX API requests. Our team is working on a fix and will update you as soon as possible. Thank you for your patience and understanding. Affected components API (Partial outage)

  2. monitoring Aug 15, 2026, 07:14 AM UTC

    Status: Monitoring The FIX API issue appears to be limited to customers using AWS Direct Connect connections at the Equinix FR5, Frankfurt location. Customers with multi-site redundancy configured for their Direct Connect paths should not be impacted. If your connectivity is affected, you may need to reconnect to the API. You can follow the AWS status here: AWS Health Dashboard "AWS Health Dashboard": https://health.aws.amazon.com/health/status?utm_source=chatgpt.com Our services are operating normally, and we’ll provide an update if anything changes on our side. Affected components API (Degraded performance)

  3. resolved Aug 21, 2026, 07:47 AM UTC

    Status: Resolved The connectivity issue affecting FIX API customers using AWS Direct Connect at the Equinix FR5 location in Frankfurt has been resolved. Connectivity has been restored, and the FIX API is operating normally. Thank you for your patience and understanding. Affected components API (Operational)