DB Maintenance
resolved- Started
- Sep 2, 12:00 AM EDT
- Resolved
- Sep 2, 12:28 AM EDT
- Duration
- 29 min
Vapi's updates (3)
- update · Sep 2, 12:00 AM EDT
We're performing scheduled maintenance on our database layer, including a capacity upgrade to a read replica and configuration updates to improve connection handling under load. Brief elevated API latency is possible. Active calls are not affected.
- update · Sep 2, 12:28 AM EDT
We completed the maintenance.
- update · Sep 2, 12:28 AM EDT
Maintenance ended
What our checks recorded
We checked Vapi 6 times from Vapi's start time to its resolution, once every five minutes. Every one of them reached Vapi's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 219 ms, against 154 ms over the 24 hours before. Vapi posted the incident at Sep 2, 12:00 AM EDT.
Updates are Vapi's own words from its status page (status: resolved); we never add an inferred cause.