Veeva incident

Veeva Maintenance - MySQL 26R1.0 Upgrade

Major Resolved View vendor source →

Veeva experienced a major incident on April 14, 2026 affecting VV2-2075 and Vault-AP PODs and 1 more component, lasting 18h. The incident has been resolved; the full update timeline is below.

Started
Apr 14, 2026, 06:00 PM UTC
Resolved
Apr 15, 2026, 12:00 PM UTC
Duration
18h
Detected by Pingoru
Apr 14, 2026, 06:00 PM UTC

Affected components

VV2-2075Vault-AP PODsVV3-3120VV3-3131VV2-2121VV1-1061VV2-2153VV2-2156VV2-2158VV2-2159VV2-2160VV2-2161VV2-2162VV1-1173VV1-1202VV1-1211VV1-1221Vault-EU PODsVV2-2063VV1-1067VV1-1142VV1-1150VV1-1157VV1-1169VV1-1176VV1-1181Veeva VaultVault-US PODs

Update timeline

  1. investigating Apr 14, 2026, 06:00 PM UTC

    Veeva Release Notification The Veeva MySQL system is scheduled to be upgraded to the latest general release. There is no expected downtime however, a short service interruption may be experienced. What: MySQL 26R1.0 When: Tuesday, April 14 APAC at 11:00 am PDT / April 15 at 3:00 am JST Affected Safety PODs: VV3-3120, VV3-3131 EU/US at 6:00 pm PDT / April 15 at 3:00 am CEST Affected Safety & LIMS PODs: VV2-2075, VV2-2156, VV2-2162, VV1-1157, VV1-1067, VV1-1142, VV1-1150, VV1-1169, VV1-1176, VV1-1181, VV2-2063, VV2-2158, VV2-2159, VV2-2160, VV2-2161, VV1-1173, VV1-1211, VV1-1221 EU/US at 7:00 pm PDT / April 15 at 4:00 am CEST Affected RegOne PODs: VV1-1061, VV1-1202, VV2-2121, VV2-2153 Estimated Duration: 60 minutes Click here to learn how to find your Vault's POD location. For up-to-date information on Veeva Systems' service status, see the Veeva Trust Site . If you have any further questions, please submit a ticket with Veeva Product Support .

  2. resolved Apr 15, 2026, 12:00 PM UTC

    This upgrade was successfully deployed in the original timeframe.