Telavox experienced a minor incident on August 3, 2026 affecting Sweden and Denmark and 1 more component, lasting 1d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 03, 2026, 07:47 AM UTC
We are currently experiencing a disruption in our deskphone and terminal services. This may affect all calls and services. Our incident response team is actively investigating the issue and working to resolve it as quickly as possible. Back to current status Status History Powered by Status.io Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by text message Afghanistan [+93] Aland Islands [+358] Albania [+355] Algeria [+213] AmericanSamoa [+1 684] Andorra [+376] Angola [+244] Anguilla [+1 264] Antarctica [+672] Antigua and Barbuda [+1268] Argentina [+54] Armenia [+374] Aruba [+297] Australia [+61] Austria [+43] Azerbaijan [+994] Bahamas [+1 242] Bahrain [+973] Bangladesh [+880] Barbados [+1 246] Belarus [+375] Belgium [+32] Belize [+501] Benin [+229] Bermuda [+1 441] Bhutan [+975] Bolivia, Plurinational State of [+591] Bosnia and Herzegovina [+387] Botswana [+267] Brazil [+55] British Indian Ocean Territory [+246] Brunei Darussalam [+673] Bulgaria [+359] Burkina Faso [+226] Burundi [+257] Cambodia [+855] Cameroon [+237] Canada [+1] Cape Verde [+238] Cayman Islands [+ 345] Central African Republic [+236] Chad [+235] Chile [+56] China [+86] Christmas Island [+61] Cocos (Keeling) Islands [+61] Colombia [+57] Comoros [+269] Congo [+242] Congo, The Democratic Republic of the [+243] Cook Islands [+682] Costa Rica [+506] Cote d'Ivoire [+225] Croatia [+385] Cuba [+53] Cyprus [+537] Czech Republic [+420] Denmark [+45] Djibouti [+253] Dominica [+1 767] Dominican Republic [+1 849] Ecuador [+593] Egypt [+20] El Salvador [+503] Equatorial Guinea [+240] Eritrea [+291] Estonia [+372] Ethiopia [+251] Falkland Islands (Malvinas) [+500] Faroe Islands [+298] Fiji [+679] Finland [+358] France [+33] French Guiana [+594] French Polynesia [+689] Gabon [+241] Gambia [+220] Georgia [+995] Germany [+49] Ghana [+233] Gibraltar [+350] Greece [+30] Greenland [+299] Grenada [+1 473] Guadeloupe [+590] Guam [+1 671] Guatemala [+502] Guernsey [+44] Guinea [+224] Guinea-Bissau [+245] Guyana [+595] Haiti [+509] Holy See (Vatican City State) [+379] Honduras [+504] Hong Kong [+852] Hungary [+36] Iceland [+354] India [+91] Indonesia [+62] Iran, Islamic Republic of [+98] Iraq [+964] Ireland [+353] Isle of Man [+44] Israel [+972] Italy [+39] Jamaica [+1 876] Japan [+81] Jersey [+44] Jordan [+962] Kazakhstan [+7 7] Kenya [+254] Kiribati [+686] Korea, Democratic People's Republic of [+850] Korea, Republic of [+82] Kuwait [+965] Kyrgyzstan [+996] Lao People's Democratic Republic [+856] Latvia [+371] Lebanon [+961] Lesotho [+266] Liberia [+231] Libyan Arab Jamahiriya [+218] Liechtenstein [+423] Lithuania [+370] Luxembourg [+352] Macao [+853] Macedonia, The Former Yugoslav Republic of [+389] Madagascar [+261] Malawi [+265] Malaysia [+60] Maldives [+960] Mali [+223] Malta [+356] Marshall Islands [+692] Martinique [+596] Mauritania [+222] Mauritius [+230] Mayotte [+262] Mexico [+52] Micronesia, Federated States of [+691] Moldova, Republic of [+373] Monaco [+377] Mongolia [+976] Montenegro [+382] Montserrat [+1664] Morocco [+212] Mozambique [+258] Myanmar [+95] Namibia [+264] Nauru [+674] Nepal [+977] Netherlands [+31] Netherlands Antilles [+599] New Caledonia [+687] New Zealand [+64] Nicaragua [+505] Niger [+227] Nigeria [+234] Niue [+683] Norfolk Island [+672] Northern Mariana Islands [+1 670] Norway [+47] Oman [+968] Pakistan [+92] Palau [+680] Palestinian Territory, Occupied [+970] Panama [+507] Papua New Guinea [+675] Paraguay [+595] Peru [+51] Philippines [+63] Pitcairn [+872] Poland [+48] Portugal [+351] Puerto Rico [+1 939] Qatar [+974] Reunion [+262] Romania [+40] Russia [+7] Rwanda [+250] Saint Barthlemy [+590] Saint Helena, Ascension and Tristan Da Cunha [+290] Saint Kitts and Nevis [+1 869] Saint Lucia [+1 758] Saint Martin [+590] Saint Pierre and Miquelon [+508] Saint Vincent and the Grenadines [+1 784] Samoa [+685] San Marino [+378] Sao Tome and Principe [+239] Saudi Arabia [+966] Senegal [+221] Serbia [+381] Seychelles [+248] Sierra Leone [+232] Singapore [+65] Slovakia [+421] Slovenia [+386] Solomon Islands [+677] Somalia [+252] South Africa [+27] South Georgia and the South Sandwich Islands [+500] Spain [+34] Sri Lanka [+94] Sudan [+249] Suriname [+597] Svalbard and Jan Mayen [+47] Swaziland [+268] Sweden [+46] Switzerland [+41] Syrian Arab Republic [+963] Taiwan, Province of China [+886] Tajikistan [+992] Tanzania, United Republic of [+255] Thailand [+66] Timor-Leste [+670] Togo [+228] Tokelau [+690] Tonga [+676] Trinidad and Tobago [+1 868] Tunisia [+216] Turkey [+90] Turkmenistan [+993] Turks and Caicos Islands [+1 649] Tuvalu [+688] Uganda [+256] Ukraine [+380] United Arab Emirates [+971] United Kingdom [+44] United States [+1] Uruguay [+598] Uzbekistan [+998] Vanuatu [+678] Venezuela, Bolivarian Republic of [+58] Viet Nam [+84] Virgin Islands, British [+1 284] Virgin Islands, U.S. [+1 340] Wallis and Futuna [+681]
- investigating Aug 03, 2026, 07:47 AM UTC
We are currently experiencing a disruption in our deskphone and terminal services. This may affect all calls and services. Our incident response team is actively investigating the issue and working to resolve it as quickly as possible.
- identified Aug 03, 2026, 08:14 AM UTC
We have identified the cause of the disruption affecting our deskphone and terminal services. Our incident response team is actively working to restore full functionality. We are currently seeing early indications that call services are beginning to recover. However, we are continuing to monitor closely and will confirm once services are fully stable. August 3, 2026 09:47 CEST
- identified Aug 03, 2026, 08:14 AM UTC
We have identified the cause of the disruption affecting our deskphone and terminal services. Our incident response team is actively working to restore full functionality. We are currently seeing early indications that call services are beginning to recover. However, we are continuing to monitor closely and will confirm once services are fully stable.
- monitoring Aug 03, 2026, 08:33 AM UTC
We can confirm that the issue has been fully resolved, with all services operating normally since 09:50. Our team will continue to monitor the situation to ensure sustained stability. August 3, 2026 10:14 CEST
- monitoring Aug 03, 2026, 08:33 AM UTC
We can confirm that the issue has been fully resolved, with all services operating normally since 09:50. Our team will continue to monitor the situation to ensure sustained stability.
- resolved Aug 03, 2026, 08:43 AM UTC
All services are now fully operational. August 3, 2026 10:33 CEST
- resolved Aug 03, 2026, 08:43 AM UTC
All services are now fully operational.
- identified Aug 03, 2026, 09:01 AM UTC
We are once again experiencing a disruption affecting our deskphone and terminal services. This may impact all calls and services. Our incident response team has resumed investigating and is working to resolve the issue as quickly as possible. August 3, 2026 10:43 CEST
- identified Aug 03, 2026, 09:01 AM UTC
We are once again experiencing a disruption affecting our deskphone and terminal services. This may impact all calls and services. Our incident response team has resumed investigating and is working to resolve the issue as quickly as possible.
- identified Aug 03, 2026, 09:30 AM UTC
We are continuing to investigate the disruption affecting our deskphone and terminal services. Our incident response team remains fully engaged and is working to resolve the issue as quickly as possible. August 3, 2026 11:01 CEST
- identified Aug 03, 2026, 09:30 AM UTC
We are continuing to investigate the disruption affecting our deskphone and terminal services. Our incident response team remains fully engaged and is working to resolve the issue as quickly as possible.
- identified Aug 03, 2026, 09:59 AM UTC
Our incident response team remains fully focused on resolving the disruption affecting our deskphone and terminal services, with the aim of restoring normal operation as soon as possible. August 3, 2026 11:30 CEST
- identified Aug 03, 2026, 09:59 AM UTC
Our incident response team remains fully focused on resolving the disruption affecting our deskphone and terminal services, with the aim of restoring normal operation as soon as possible.
- identified Aug 03, 2026, 10:31 AM UTC
We are now seeing gradual improvements across service levels, though work remains ongoing to restore full, stable operation. August 3, 2026 11:59 CEST
- identified Aug 03, 2026, 10:31 AM UTC
We are now seeing gradual improvements across service levels, though work remains ongoing to restore full, stable operation.
- monitoring Aug 03, 2026, 11:00 AM UTC
Service traffic is steadily returning to normal. Our team is maintaining monitoring throughout the day to safeguard continued stability. August 3, 2026 12:31 CEST
- monitoring Aug 03, 2026, 11:00 AM UTC
Service traffic is steadily returning to normal. Our team is maintaining monitoring throughout the day to safeguard continued stability.
- monitoring Aug 03, 2026, 12:48 PM UTC
Issues affecting our deskphone and terminal services are still ongoing. The team is monitoring closely and working to get things back to normal. A further update will follow soon. August 3, 2026 13:00 CEST
- monitoring Aug 03, 2026, 12:48 PM UTC
Issues affecting our deskphone and terminal services are still ongoing. The team is monitoring closely and working to get things back to normal. A further update will follow soon.
- monitoring Aug 03, 2026, 01:23 PM UTC
We have implemented changes to address the root cause of the disruption affecting our deskphone and terminal services. Initial signs are positive, and we are closely monitoring call and service traffic to confirm the improvement is sustained. We will continue to monitor closely over the coming hours and provide a further update once we can confirm full stability. August 3, 2026 14:48 CEST
- monitoring Aug 03, 2026, 01:23 PM UTC
We have implemented changes to address the root cause of the disruption affecting our deskphone and terminal services. Initial signs are positive, and we are closely monitoring call and service traffic to confirm the improvement is sustained. We will continue to monitor closely over the coming hours and provide a further update once we can confirm full stability.
- monitoring Aug 03, 2026, 02:07 PM UTC
The changes we implemented did not have the effect we were hoping for, and issues affecting our deskphone and terminal services are still ongoing. The team is continuing to investigate and working to get things back to normal.
- monitoring Aug 03, 2026, 03:04 PM UTC
The root cause has now been identified, and we've applied a fix that we're confident resolves the issue. Services are stable again, and although everything appears to be working as expected, we'll keep monitoring closely through the afternoon, evening and night to make sure it stays that way. A concluding update will be provided tomorrow.
- monitoring Aug 03, 2026, 03:17 PM UTC
Updating status to Operational to reflect current status