Veeva experienced a major incident on May 8, 2026 affecting VV1-1150 and Veeva Vault and 1 more component, lasting 3d 13h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 08, 2026, 03:30 AM UTC
Veeva Vault POD VV1-1150 is currently experiencing a service disruption. Veeva engineering teams are working to return the service to normal as quickly as possible.
- resolved May 08, 2026, 05:49 AM UTC
Affected Veeva Vault PODs are now fully available with all services operating normally.
- resolved May 11, 2026, 04:31 PM UTC
Below is the original Trust notification that was posted on the main Trust page from May 7-11. We are investigating reports of service disruption and increased latency affecting certain Veeva US PODs. This issue is related to an ongoing AWS regional event in the US-EAST-1 (N. Virginia) region involving power and cooling issues that started around 5:15 pm PT on Thursday, May 7. While the impact may be intermittent, we are closely monitoring all PODs in this region. We will provide specific status updates for any individual PODs experiencing confirmed downtime or significant service degradation. For the latest updates regarding the underlying infrastructure, please visit the AWS Health Dashboard. We apologize for any inconvenience this may cause to your operations. We will provide another update by 11:00 pm PT or as soon as more information becomes available. May 7, 11:00 pm PT Update: The remaining impacted PODs are currently recovering and should be available shortly: VV1-1150, VV1-1176, & VV1-1181. We will continue to monitor the AWS issue and provide any relevant updates by 12:00 am PT. May 7, 11:55 pm PT Update: The 3 PODs which experienced extended downtime were confirmed to be online by 11:05 pm PT. Based on the latest status from AWS, we expect no further impacts however we are currently monitoring an intermittent performance issue with VV1-16, as a separate issue. If no further issues occur, we will mark this status as resolved after ~12 hours of monitoring. May 8, 11:50 am PT Update: Following 12 hours of stable performance and no further impact to our US-EAST-1 PODs, we are marking this incident as resolved. The performance issue previously affecting VV1-16 was resolved at 12:00 am PT. We will continue to monitor AWS's ongoing infrastructure recovery as a precaution. Thank you for your patience and we apologize for the inconvenience.