Is Telavox down?

Last checked 9m ago
Current status
Telavox is up

No incidents right now.

Official status page: https://status.telavox.com · Polled every 5 minutes · 115 components tracked

Telavox is operational right now. Last checked 9m ago; the most recent incident resolved 1d ago.

Real-time Telavox status, recent outages, and incident history — pulled directly from Telavox's official status page at https://status.telavox.com every 5 minutes. Pingoru tracks 115 Telavox services and has captured 11 incidents in the last 90 days (99.19% uptime). Get email, Slack, Discord, or webhook alerts the moment Telavox reports a new incident — free for 5 monitors, no credit card.

Users who monitor Telavox also follow these Communications services: GoDaddy Miro Talkdesk GoToConnect SMTP2GO Singlewire Software Slido HelpScout Nuance Flowroute View all 6,000+ providers
Telavox uptime 99.19% uptime · past 90 days
Mon Wed Fri
MayJunJulAug
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1d
    Started Aug 03, 2026, 07:47 AM UTC · Resolved Aug 04, 2026, 08:16 AM UTC
    SwedenDenmarkNorwayFinlandUnited KingdomBelgiumFranceSpainNetherlandsDesk Phones
    Timeline · 25 updates
    • 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

    Latest: Updating status to Operational to reflect current status

  2. Resolved 2h 57m
    Started Jul 14, 2026, 03:12 PM UTC · Resolved Jul 14, 2026, 06:09 PM UTC
    DenmarkMobile TelephonyFixed Telephony
    Timeline · 11 updates
    • investigating · Jul 14, 2026, 03:12 PM UTC

      We are currently experiencing a service disruption affecting mobile and fixed voice quality in Denmark. Our vendor has confirmed the issue and is actively investigating the root cause. We will provide an update as soon as more information becomes available. 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] Wa

    • investigating · Jul 14, 2026, 03:12 PM UTC

      We are currently experiencing a service disruption affecting mobile and fixed voice quality in Denmark. Our vendor has confirmed the issue and is actively investigating the root cause. We apologize for the inconvenience and will provide an update as soon as more information becomes available.

    • investigating · Jul 14, 2026, 03:44 PM UTC

      Our vendor continues to investigate the root cause and is working to resolve the issue. We will provide another update as soon as more information becomes available. July 14, 2026 17:12 CEST

    • investigating · Jul 14, 2026, 03:44 PM UTC

      Our vendor continues to investigate the root cause and is working to resolve the issue. We will provide another update as soon as more information becomes available.

    • investigating · Jul 14, 2026, 04:25 PM UTC

      Our vendor continues to actively work on resolving the issue. Together with the vendor, we are exploring possible ways to reduce the impact while efforts to resolve the issue continue. We will provide another update as soon as more information becomes available. July 14, 2026 17:44 CEST

    • investigating · Jul 14, 2026, 04:25 PM UTC

      Our vendor continues to actively work on resolving the issue. Together with the vendor, we are exploring possible ways to reduce the impact while efforts to resolve the issue continue. We will provide another update as soon as more information becomes available.

    • investigating · Jul 14, 2026, 05:18 PM UTC

      There are no new updates at this time. Our vendor continues to actively work on resolving the issue, and we will share further information as soon as it becomes available. July 14, 2026 18:25 CEST

    • investigating · Jul 14, 2026, 05:18 PM UTC

      There are no new updates at this time. Our vendor continues to actively work on resolving the issue, and we will share further information as soon as it becomes available.

    • monitoring · Jul 14, 2026, 05:52 PM UTC

      The issue has been resolved following mitigation implemented by our vendor. We will continue to monitor the service to ensure stability before closing this incident. July 14, 2026 19:18 CEST

    • monitoring · Jul 14, 2026, 05:52 PM UTC

      The issue has been resolved following mitigation implemented by our vendor. We will continue to monitor the service to ensure stability before closing this incident.

    • resolved · Jul 14, 2026, 06:09 PM UTC

      All systems are functioning normally, and the incident is now closed. If you continue to experience any further issues, contact your support team for further assistance. July 14, 2026 19:52 CEST

    Latest: All systems are functioning normally, and the incident is now closed. If you continue to experience any further issues, contact your support team for further assistance. July 14, 2…

  3. Resolved 1h 37m
    Started Jul 14, 2026, 01:34 AM UTC · Resolved Jul 14, 2026, 03:12 AM UTC
    SwedenDenmarkNorwayFinlandUnited KingdomBelgiumFranceSpainNetherlandsFixed Telephony
    Timeline · 9 updates
    • investigating · Jul 14, 2026, 01:34 AM UTC

      We are currently investigating an intermittent issue affecting our Fixed Telephony services. Customers may experience difficulties when placing or receiving fixed-line calls, including connected calls with no audio. Our incident response team is actively investigating the issue. We are working to identify the root cause and restore full service as quickly as possible. We will provide updates as soon as more information becomes available. 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] Uni

    • investigating · Jul 14, 2026, 01:34 AM UTC

      We are currently investigating an intermittent issue affecting our Fixed Telephony services. Customers may experience difficulties when placing or receiving fixed-line calls, including connected calls with no audio. Our incident response team is actively investigating the issue. We are working to identify the root cause and restore full service as quickly as possible. We will provide updates as soon as more information becomes available.

    • investigating · Jul 14, 2026, 02:02 AM UTC

      We are continuing to investigate the issue affecting our Fixed Telephony services. Our incident response team are actively working to identify the root cause, assess the impact, and restore normal service. We will provide updates as soon as more information becomes available. July 14, 2026 03:34 CEST

    • investigating · Jul 14, 2026, 02:02 AM UTC

      We are continuing to investigate the issue affecting our Fixed Telephony services. Our incident response team are actively working to identify the root cause, assess the impact, and restore normal service. We will provide updates as soon as more information becomes available.

    • investigating · Jul 14, 2026, 02:34 AM UTC

      We are continuing to investigate the issue affecting our Fixed Telephony services. There are no significant changes to report at this time. Our incident response team continues to investigate the cause of the issue and working towards restoring normal service. Further updates will be provided as more information becomes available. July 14, 2026 04:02 CEST

    • investigating · Jul 14, 2026, 02:34 AM UTC

      We are continuing to investigate the issue affecting our Fixed Telephony services. There are no significant changes to report at this time. Our incident response team continues to investigate the cause of the issue and working towards restoring normal service. Further updates will be provided as more information becomes available.

    • monitoring · Jul 14, 2026, 02:59 AM UTC

      The issue affecting our Fixed Telephony services has been resolved. Our incident response team has implemented corrective actions that have restored normal service. We will continue to monitor to ensure services remain stable, before closing this incident. July 14, 2026 04:34 CEST

    • monitoring · Jul 14, 2026, 02:59 AM UTC

      The issue affecting our Fixed Telephony services has been resolved. Our incident response team has implemented corrective actions that have restored normal service. We will continue to monitor to ensure services remain stable, before closing this incident.

    • resolved · Jul 14, 2026, 03:12 AM UTC

      The issue affecting our Fixed Telephony services has been resolved. Services have remained stable following the corrective actions taken by our teams. We are closing this incident. July 14, 2026 04:59 CEST

    Latest: The issue affecting our Fixed Telephony services has been resolved. Services have remained stable following the corrective actions taken by our teams. We are closing this incident.…

  4. Resolved 20h 27m
    Started Jun 24, 2026, 06:24 PM UTC · Resolved Jun 25, 2026, 02:52 PM UTC
    SwedenDenmarkNorwayFinlandUnited KingdomBelgiumFranceSpainNetherlandsSoftphone & Applications
    Timeline · 3 updates
    • monitoring · Jun 24, 2026, 06:24 PM UTC

      A fix has been deployed for the recent issue affecting the Telavox Desktop Application on MacOS. At approximately 16:00 CEST on June 24, 2026, a software update (version 2.3.1) was released. This specific version introduced an issue exclusively for MacOS users, causing the User Interface to fail to load while the application continued to run in the background. A corrected version (2.3.2) was released at aproximately 4 hours later at 20:02 CEST to resolve this behavior. Note for users on version 2.3.0: If your application is currently running version 2.3.0, it will automatically update directly to version 2.3.2. You do not need to take any manual action and will not be affected by this issue. Required Action for Affected Users Due to the nature of the issue, the automatic update mechanism is unable to pull the fix automatically on affected MacOS devices. To restore service, please perform the following manual steps: 1) Uninstall version 2.3.1 from your MacOS device. 2) Download and install the new, fixed version (2.3.2) directly from telavox.se/appar Workaround for Users Without Administrative Rights If you are unable to reinstall the application due to administrative restrictions on your device, you can use our web client as a temporary workaround: 1) Log in to the web client at app.telavox.com. 2) Go to the Settings (gear) icon. 3) Go to Telephony & Audio 4) Make sure that Incoming Calls is turned on to receive calls directly through your browser. 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 [+59

    • monitoring · Jun 24, 2026, 06:24 PM UTC

      A fix has been deployed for the recent issue affecting the Telavox Desktop Application on MacOS. At approximately 16:00 CEST on June 24, 2026, a software update (version 2.3.1) was released. This specific version introduced an issue exclusively for MacOS users, causing the User Interface to fail to load while the application continued to run in the background. A corrected version (2.3.2) was released at aproximately 4 hours later at 20:02 CEST to resolve this behavior. Note for users on version 2.3.0: If your application is currently running version 2.3.0, it will automatically update directly to version 2.3.2. You do not need to take any manual action and will not be affected by this issue. Required Action for Affected Users Due to the nature of the issue, the automatic update mechanism is unable to pull the fix automatically on affected MacOS devices. To restore service, please perform the following manual steps: 1) Uninstall version 2.3.1 from your MacOS device. 2) Download and install the new, fixed version (2.3.2) directly from telavox.se/appar Workaround for Users Without Administrative Rights If you are unable to reinstall the application due to administrative restrictions on your device, you can use our web client as a temporary workaround: 1) Log in to the web client at app.telavox.com. 2) Go to the Settings (gear) icon. 3) Make sure that Incoming Calls is turned on to receive calls directly through your browser.

    • resolved · Jun 25, 2026, 02:52 PM UTC

      This incident has been resolved since Yesterday 2026-06-24 at 20:02 CEST. The fix is live in version 2.3.2. For the vast majority of users, no action is required. However, if you are still experiencing a blank user interface on MacOS, you may need to manually reinstall the app. Required Action for Affected Users: Uninstall version 2.3.1 from your MacOS device. Download and install the new version (2.3.2) directly from telavox.se/appar. If you are still experiencing issues after completing these steps, please don't hesitate to reach out to our support team for further assistance. June 24, 2026 20:24 CEST

    Latest: This incident has been resolved since Yesterday 2026-06-24 at 20:02 CEST. The fix is live in version 2.3.2. For the vast majority of users, no action is required. However, if you a…

  5. Resolved 11m
    Started Jun 17, 2026, 07:49 AM UTC · Resolved Jun 17, 2026, 08:01 AM UTC
    SwedenMobile Services
    Timeline · 4 updates
    • investigating · Jun 17, 2026, 07:49 AM UTC

      We are currently investigating an incident affecting mobile data connectivity in Sweden. Users may experience slow or failed data connections. 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] Wall

    • investigating · Jun 17, 2026, 07:49 AM UTC

      We are currently investigating an incident affecting mobile data connectivity in Sweden. Users may experience slow or failed data connections. Our incident response team is actively investigating the issue and working to resolve it as quickly as possible.

    • monitoring · Jun 17, 2026, 07:57 AM UTC

      Following the implementation of corrective actions, mobile data services are now recovering and functioning as expected. We will continue monitoring the situation to verify that all services are fully restored and stable. Data services are now recovering and functioning as expected. June 17, 2026 09:49 CEST

    • resolved · Jun 17, 2026, 08:01 AM UTC

      The issue affecting mobile data services in Sweden has been resolved as of 09:48 CEST. If you continue to experience any further issues, contact our support team for further assistance at [email protected] We will now proceed with closing this incident. June 17, 2026 09:57 CEST

    Latest: The issue affecting mobile data services in Sweden has been resolved as of 09:48 CEST. If you continue to experience any further issues, contact our support team for further assist…

See the full Telavox outage history

4 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Telavox outage history →

Or sign up free to get alerts when Telavox breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 9 incidents View full outage history →