Changes Vonage Norway Voice - Degradation towards all network affecting Long Virtual Numbers

Vonage: Incident updated: Norway Voice - Degradation towards all network affecting Long Virtual Numbers

Incident updateNot classified yetChanged 2026-10-29 20:44 UTCvonageapi.statuspage.io

Summary

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.

AddedUpdateidentified2026-10-29 20:35 UTC#1

not present

We have worked with our carrier partner to identify workaround measures for the degradation impacting voice calls towards all networks affecting a subset of Vonage Norway Long Virtual Numbers (LVNs). While we work toward a permanent resolution for Sweden and Norway, a workaround is available right now: simply use an alternative international number when placing calls to these destinations. We encourage all impacted customers to implement this as soon as possible. If you have any questions or require further assistance, please do not hesitate to contact api.support@vonage.com. We apologize for any inconvenience caused and thank you for your patience and understanding throughout this incident.

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.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run (00:41 UTC) commits it.