ChangesVonageVerify V2 Silent Auth Issue
Vonage: Incident silently edited: Verify V2 Silent Auth Issue
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what Vonage removed; blue is what they added. Muted text is unchanged context.
Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
Before captured
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
6b22e69a12a82676…After captured
In the 2026-10-21 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d16938d39af88e9e…
History of this incident
Wednesday, October 21
1 rewrite
- Minor editEdited by the vendor
Verify V2 Silent Auth Issuethis change
Monday, October 19
1 rewrite
- Wording onlyEdited by the vendor
Vonage revised its resolved Verify V2 incident notice to describe a service interruption reported by its third party and promise impacted customers a formal RFO. Customers may have seen increased 500 errors during silent authentication requests from 2026-10-19 09:00 UTC until full resolution at 2026-10-19 09:20 UTC; no impact level was stated.
Cite this
Incident silently edited: Verify V2 Silent Auth Issue on Vonage’s status page, changed 2026-10-21 10:43 UTC (change 2 of 2).
- Title
- Incident silently edited: Verify V2 Silent Auth Issue
- Vendor
- Vonage
- Date
- URL
- https://rewindex.com/change/r3cfcb0f99755ea