Bitvavo incident

Technical issue Affecting transaction history

Minor Resolved View vendor source →

Bitvavo experienced a minor incident on July 15, 2026 affecting Transaction History, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jul 15, 2026, 02:33 PM UTC
Resolved
Jul 15, 2026, 02:33 PM UTC
Duration
Detected by Pingoru
Jul 15, 2026, 02:33 PM UTC

Affected components

Transaction History

Update timeline

  1. investigating Jul 13, 2026, 02:39 PM UTC

    Status: Investigating We are investigating an issue affecting transaction history on our platform. Users may experience delays in viewing recent transactions, or some transaction history may be temporarily unavailable. Our team is working to resolve the issue and will provide an update as soon as possible. Thank you for your patience and understanding. Affected components Transaction History (Degraded performance)

  2. identified Jul 13, 2026, 03:09 PM UTC

    Status: Identified We have identified the cause of the issue affecting transaction history. Our team is actively working to implement a fix and restore normal service as quickly as possible. We will provide another update as soon as we have more information. Thank you for your continued patience and understanding. Affected components Transaction History (Degraded performance)

  3. identified Jul 13, 2026, 06:22 PM UTC

    Status: Identified We are currently implementing a fix for the issue affecting transaction history. During this time, users may still experience delays, and transaction history from before the incident may not yet be visible while the changes are being rolled out. We expect the issue to be resolved shortly and will provide another update once the fix has been fully implemented. Thank you for your continued patience and understanding. Affected components Transaction History (Degraded performance)

  4. resolved Jul 15, 2026, 02:33 PM UTC

    Status: Resolved After thorough testing and continued monitoring, we have confirmed that the fix has been successfully implemented and that transaction history is functioning as expected. As a result, this incident has now been resolved and closed. If you encounter any further issues or have any questions, please don't hesitate to reach out to us. Thank you again for your patience, cooperation, and understanding throughout this process. Affected components Transaction History (Operational)