Vonage: Norway Voice - Degradation towards all network affecting Long Virtual Numbers
Affected components: Global Connectivity - Voice EuropeVoice Europe
Timeline of updates
- investigating
Please be informed that there was service degradation for outbound calls towards all network affecting Norway long virtual numbers.
The carrier is aware of this issue and investigating the root cause. We will issue an update as soon as more information becomes available.
If you have any questions, please contact api.support.vonage.com - investigating
Please be informed that we have identified the root cause of the problem, and our team are working directly with the suppliers and carriers to resolve it as soon as possible.
We will be sending another update as soon as we make more progress or further information on the resolution.
If you have any questions, please contact api.support.vonage.com - identified
Please be informed that we have identified the root cause of the problem, and our teams are working directly with the suppliers and carriers to resolve it as soon as possible.
We will be sending another update as soon as we make more progress or have further information on the final resolution.
If you have any questions, please contact api.support.vonage.com - identified
Please be informed that we have identified the root cause of the problem, and our teams are working directly with the suppliers and carriers to resolve it as soon as possible.
We will be sending another update as soon as we make more progress or have further information on the final resolution.
If you have any questions, please contact api.support.vonage.com - identified
Please be informed that we have identified the root cause of the problem, and our teams are working directly with the suppliers and carriers to resolve it as soon as possible.
We will be sending another update as soon as we make more progress or have further information on the final resolution.
If you have any questions, please contact api.support.vonage.com - identified
Please be informed that we have identified the root cause of the problem, and our teams are working directly with the suppliers and carriers to resolve it as soon as possible.
We will be sending another update as soon as we make more progress or have further information on the final resolution.
If you have any questions, please contact api.support.vonage.com - identified
Please be informed that we have identified the root cause of the problem, and our teams are working directly with the suppliers and carriers to resolve it as soon as possible.
We will be sending another update as soon as we make more progress or have further information on the final resolution.
If you have any questions, please contact api.support.vonage.com - identified
Please be informed that we have identified the root cause of the problem, and our teams are working directly with the suppliers and carriers to resolve it as soon as possible.
Inbound calls have recovered, and we will continue working closely with our supplier to address the degradation on outbound calls.
We will be sending another update as soon as we make more progress or have further information on the final resolution.
If you have any questions, please contact api.support.vonage.com - identified
Please be informed that we have identified the root cause of the problem, and our teams are working directly with the suppliers and carriers to resolve it as soon as possible.
Inbound calls have recovered, and we will continue working closely with our supplier to address the degradation on outbound calls.
We will be sending another update as soon as we make more progress or have further information on the final resolution.
If you have any questions, please contact api.support.vonage.com - identifiedEdited
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 https://api.support.vonage.com (opens in new tab).
We apologize for any inconvenience caused and thank you for your patience and understanding throughout this incident.
Changes Rewindex caught on this incident
- Incident updated: Norway Voice - Degradation towards all network affecting Long Virtual Numbers
- Incident updated: Norway Voice - Degradation towards all network affecting Long Virtual Numbers
- Incident updated: Norway Voice - Degradation towards all network affecting Long Virtual Numbers
- Incident updated: Norway Voice - Degradation towards all network affecting Long Virtual Numbers
- Incident updated: Norway Voice - Degradation towards all network affecting Long Virtual Numbers
- Incident updated: Norway Voice - Degradation towards all network affecting Long Virtual Numbers
- Incident updated: Norway Voice - Degradation towards all network affecting Long Virtual Numbers
- Incident updated: Norway Voice - Degradation towards all network affecting Long Virtual Numbers
- Incident silently edited: Norway Voice - Degradation towards all network affecting Long Virtual Numbers
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.
First version captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
6ce2f8505798ee16…Version 2 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d2e8f572a61026ef…Version 3 captured
In the 2026-10-24 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
4767da365492f926…Version 4 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
6d970aa10b610801…Version 5 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
fc11aa4e0a2c140b…Version 6 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
8f6f3f1bb56b2149…Version 7 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
39edd9301c211a25…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on vonageapi.statuspage.io (opens in new tab).