Is Elastx down?

Since the maintenance earlier this week we are seeing issues with images larger than 5GB that are uploaded to the Openstack image service. Snapshots of servers with local storage (not volume backed) are affected by this as well as it uses the same process for creating snapshots. They may look as if they have completed successfully but are likely failed and cut off at around 200MB in size. We are currently investigating closer and are working on a fix for this. June 5, 2026 12:03 CEST

Since the maintenance earlier this week we are seeing issues with images larger than 5GB that are uploaded to the Openstack image service. Snapshots of servers with local storage (not volume backed) are affected by this as well as it uses the same process for creating snapshots. They may look as if they have completed successfully but are likely failed and cut off at around 200MB in size. We are currently investigating closer and are working on a fix for this.

We have managed to pinpoint the issue and implemented a working fix in our test envinroment and will be rolling it out to our production environment shortly. Some minor disturbances for the image service may be noticed during the rollout. June 5, 2026 12:24 CEST

We have managed to pinpoint the issue and implemented a working fix in our test envinroment and will be rolling it out to our production environment shortly. Some minor disturbances for the image service may be noticed during the rollout.

The fix is now live and we have confirmed that both image and snapshot uploads are working as expected again. We will keep monitoring the situation to see if we have missed any odd cases. If you are still experiencing any problems with the image service or snapshots then please reach out to us so we can investigate your issue closer. June 8, 2026 10:27 CEST

The fix is now live and we have confirmed that both image and snapshot uploads are working as expected again. We will keep monitoring the situation to see if we have missed any odd cases. If you are still experiencing any problems with the image service or snapshots then please reach out to us so we can investigate your issue closer.

We have not seen any further issue since deploying the fix and will go ahead and close this incident. Back to current status Status History Report Issue 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] Yemen [+967] Zambia [+260] Zimbabwe [+263] Example: 201-555-1717 Close Subscribe Manage Subscription Manage Existing Sub

There are issues after the planned maintenance of the DBaaS management system. Connections to your databases are not affected. The issues are purely in the management system. Management functionality might come and go while we are fixing the issues. Backups and other jobs handled by the management system might be delayed. Avoid doing any changes to your setup until the issues are solved. May 19, 2026 17:47 CEST

There are issues after the planned maintenance of the DBaaS management system. Connections to your databases are not affected. The issues are purely in the management system. Management functionality might come and go while we are fixing the issues. Backups and other jobs handled by the management system might be delayed. Avoid doing any changes to your setup until the issues are solved.

We have discovered a few selected data stores that are experiencing connectivity issues. Investigation ongoing May 19, 2026 20:08 CEST

We have discovered a few selected data stores that are experiencing connectivity issues. Investigation ongoing

Scope has been narrowed and focus has shifted to building and implementing a potential fix. Currently we are still seeing a small amount of datastores impacted. We still advice to not perform any changes or scheduled work with datastores until this incident is resolved. New update will be approx. 21:30 CEST. May 19, 2026 21:30 CEST

Scope has been narrowed and focus has shifted to building and implementing a potential fix. Currently we are still seeing a small amount of datastores impacted. We still advice to not perform any changes or scheduled work with datastores until this incident is resolved. New update will be approx. 21:30 CEST.

The implementation of the fix has not had expected results and we are moving back the status to investigating and are analyzing the results to find a new solution. We still advice to not perform any changes or scheduled work with datastores until this incident is resolved. New update will be approx. 23:00 CEST. May 19, 2026 23:01 CEST

The implementation of the fix has not had expected results and we are moving back the status to investigating and are analyzing the results to find a new solution. We still advice to not perform any changes or scheduled work with datastores until this incident is resolved. New update will be approx. 23:00 CEST.

More work on a fix is in progress from findings and is being tested and evaluated at the moment. For now we need to re-run multiple tests in parallel and will send out a new update once we have a more clear picture of a solution-ETA. We continue to advice against modifying or doing changes to the datastore configuration(s) at the moment. May 20, 2026 01:15 CEST

More work on a fix is in progress from findings and is being tested and evaluated at the moment. For now we need to re-run multiple tests in parallel and will send out a new update once we have a more clear picture of a solution-ETA. We continue to advice against modifying or doing changes to the datastore configuration(s) at the moment.

Update: Problem trigged by earlier maintenance requires rebuilding and code-reviews for a stable fix; to avoid issues with changes being done to datastores the management-ui is currently disabled externally. We will continue working on this and schedule a sit-rep tomorrow at 0900 internally with external resources and re-asses at that time. May 20, 2026 09:26 CEST

Update: Problem trigged by earlier maintenance requires rebuilding and code-reviews for a stable fix; to avoid issues with changes being done to datastores the management-ui is currently disabled externally. We will continue working on this and schedule a sit-rep tomorrow at 0900 internally with external resources and re-asses at that time.

Morning update: currently moving forward with 2 parallel possible solutions and are evaluating both in test-environments at the moment. We will re-assess both options and provide an update at 1200 at the latest. May 20, 2026 11:58 CEST

Morning update: currently moving forward with 2 parallel possible solutions and are evaluating both in test-environments at the moment. We will re-assess both options and provide an update at 1200 at the latest.

Mid-day update: The database-management service has been partially restored however we are still seeing unknown/unstable states and issues connecting to datastores intermittently. Status changed to Status Disruption and our current focus is restoring services to stable state for all datastores. We still advice against doing modifications on datastores until incident is set to resolved. May 20, 2026 13:33 CEST

Mid-day update: The database-management service has been partially restored however we are still seeing unknown/unstable states and issues connecting to datastores intermittently. Status changed to Status Disruption and our current focus is restoring services to stable state for all datastores. We still advice against doing modifications on datastores until incident is set to resolved.

Update: Issues reaching multiple data-stores has just been resolved by a manual fix and we will continue to monitor it as we are still continuing with the service-disruption on the management-system. If you still have issues connecting to your datastore we advice you to reach out with as much information as possible in order for us to assist. Incident remains open and we continue working on the underlying issue with the management-service. May 20, 2026 22:38 CEST

Update: Issues reaching multiple data-stores has just been resolved by a manual fix and we will continue to monitor it as we are still continuing with the service-disruption on the management-system. If you still have issues connecting to your datastore we advice you to reach out with as much information as possible in order for us to assist. Incident remains open and we continue working on the underlying issue with the management-service.

Currently datastores are in a stable state and we are moving down to monitoring in terms of incident-status. Our 24/7 staffing remains available and developers will work on analyzing logs and results of todays work throughout the night for a handover tomorrow at 0900. A new update will be provided in the morning with next expected steps and actions to be done in regards to fully stabilize the management-service. May 21, 2026 10:00 CEST

Currently datastores are in a stable state and we are moving down to monitoring in terms of incident-status. Our 24/7 staffing remains available and developers will work on analyzing logs and results of todays work throughout the night for a handover tomorrow at 0900. A new update will be provided in the morning with next expected steps and actions to be done in regards to fully stabilize the management-service.

Nightly work continues today with locating exact root-cause and issues with management-service to bring it back to full stable state. Throughout the day all work will be done in test & stage environments unless a resolution and fix becomes ready for production-deployment in which case a MW or EMW will be communicated. May 21, 2026 17:31 CEST

Nightly work continues today with locating exact root-cause and issues with management-service to bring it back to full stable state. Throughout the day all work will be done in test & stage environments unless a resolution and fix becomes ready for production-deployment in which case a MW or EMW will be communicated.

Root-cause causing management-service issues identified and a fix has been created and passed testing. Currently we are refining the fix and preparing for an Emergency Window scheduled for 21:00-00:00 tonight. May 21, 2026 21:50 CEST

Root-cause causing management-service issues identified and a fix has been created and passed testing. Currently we are refining the fix and preparing for an Emergency Window scheduled for 21:00-00:00 tonight.

Tonights Emergency Maintenance Window has been cancelled; final testing-results was not 100% satisfactory and we will continue working and improving the fix overnight and re-assess with the full team tomorrow at 0900. For now we are reverting back to Monitoring the situation and will continue to ensure datastores remain intact. May 22, 2026 16:30 CEST

Tonights Emergency Maintenance Window has been cancelled; final testing-results was not 100% satisfactory and we will continue working and improving the fix overnight and re-assess with the full team tomorrow at 0900. For now we are reverting back to Monitoring the situation and will continue to ensure datastores remain intact.

Update: A workaround has been built, tested and confirmed to be ready to deploy for resolving the issue with our management-service for DBaaS. This will stabilize the GUI for the service and restore certain background-tasks that have had issues with scheduling and maintenance-jobs. A Emergency Maintenance Window will be set and communicated for tonight 20:00-00:00. May 22, 2026 21:46 CEST

Update: A workaround has been built, tested and confirmed to be ready to deploy for resolving the issue with our management-service for DBaaS. This will stabilize the GUI for the service and restore certain background-tasks that have had issues with scheduling and maintenance-jobs. A Emergency Maintenance Window will be set and communicated for tonight 20:00-00:00.

After tonight's Emergency Maintenance management-services are restored. As this was a complicates issue we are maintaining this incident open in monitoring for now as we will continue checking the health and status of services over the weekend. May 25, 2026 09:52 CEST

After tonight's Emergency Maintenance management-services are restored. As this was a complicates issue we are maintaining this incident open in monitoring for now as we will continue checking the health and status of services over the weekend.

After the weekend we have reviewed the status and can note several issues still present with the management-service in the UI. Status of backup-jobs are not showing correctly and some datastores not showing correct status. We are planning for a emergency-maintenance to re-scale the management-service in the afternoon; will be communicated separately. We still advice to not manage changes or re-configurations through the UI-management interface for now. May 25, 2026 20:04 CEST

After the weekend we have reviewed the status and can note several issues still present with the management-service in the UI. Status of backup-jobs are not showing correctly and some datastores not showing correct status. We are planning for a emergency-maintenance to re-scale the management-service in the afternoon; will be communicated separately. We still advice to not manage changes or re-configurations through the UI-management interface for now.

Summary from todays work: Emergency Maintenance performed between 14:00 - 17:00 resolved our remaining general issues with our management-service and this is stable now since 3 hours back. A limited amount of datastores are still lacking certain monitoring-features which we will continue to work on and provide further updates tomorrow. From an incident-perspective we are restoring services to Operational and status Monitoring over night. May 26, 2026 22:32 CEST

Summary from todays work: Emergency Maintenance performed between 14:00 - 17:00 resolved our remaining general issues with our management-service and this is stable now since 3 hours back. A limited amount of datastores are still lacking certain monitoring-features which we will continue to work on and provide further updates tomorrow. From an incident-perspective we are restoring services to Operational and status Monitoring over night.

Evening update; We have monitored multiple service-disruptions during the last 12 hours, some with limited impact to datastore-availability (datestore operational but unreachable). We have performed another Emergency Maintenance today with positive results stabilizing servicesand again noticed limited datastore-service disruptions during the work. At the moment we are in a stable state from a platform perspective but are still noticing limited and individual datastore disruptions, customers impacted have been proactively contacted with information. We are still in investigating mode as this is a incident that has been ongoing with active work for 7 days straight and we have not resolved all open issues, our efforts continue to fully stabilize the service. Status is Partial Service Disruption. 24/7 monitoring is still in effect. May 27, 2026 16:18 CEST

Evening update; We have monitored multiple service-disruptions during the last 12 hours, some with limited impact to datastore-availability (datestore operational but unreachable). We have performed another Emergency Maintenance today with positive results stabilizing servicesand again noticed limited datastore-service disruptions during the work. At the moment we are in a stable state from a platform perspective but are still noticing limited and individual datastore disruptions, customers impacted have been proactively contacted with information. We are still in investigating mode as this is a incident that has been ongoing with active work for 7 days straight and we have not resolved all open issues, our efforts continue to fully stabilize the service. Status is Partial Service Disruption. 24/7 monitoring is still in effect.

Afternoon update; We have monitored the situation and cleaned up after the incident as well as restored remaining impacted services. At the moment we are in a stable state from a platform perspective but still recommend to avoid making changes. As we have the odd datastore with issues, we will keep status as investigating and as partial service disruption overnight. We continue monitoring the service closely. May 28, 2026 16:58 CEST

Afternoon update; We have monitored the situation and cleaned up after the incident as well as restored remaining impacted services. At the moment we are in a stable state from a platform perspective but still recommend to avoid making changes. As we have the odd datastore with issues, we will keep status as investigating and as partial service disruption overnight. We continue monitoring the service closely.

Afternoon update: We have monitored the situation as well as worked on a permanent fix which will be thoroughly tested tomorrow. The platform is stable, but still reports wrong status for the odd datastore and we recommend to avoid making changes. We will change the status to monitoring, but partial disruption, as we are in full understanding of the situation and are working on a permanent fix. May 29, 2026 16:00 CEST

Afternoon update: We have monitored the situation as well as worked on a permanent fix which will be thoroughly tested tomorrow. The platform is stable, but still reports wrong status for the odd datastore and we recommend to avoid making changes. We will change the status to monitoring, but partial disruption, as we are in full understanding of the situation and are working on a permanent fix.

Friday afternoon update before the weekend: We have sustained the extended monitoring and the situation remains stable with an operational platform despite the UI reporting errors in a few cases. Backups have been further cleaned. We continue to monitor the situation during the weekend and will decide on the exact timing of an emergency maintenance window for a permanent fix early next week. Next update on Monday. June 2, 2026 15:20 CEST

Friday afternoon update before the weekend: We have sustained the extended monitoring and the situation remains stable with an operational platform despite the UI reporting errors in a few cases. Backups have been further cleaned. We continue to monitor the situation during the weekend and will decide on the exact timing of an emergency maintenance window for a permanent fix early next week. Next update on Monday.

Status remains stable and we have worked through a hotfix to restore service to normal again. Maintenance window for this fix starts at 17.00 CET. Next update in conjunction with the maintenance window. June 2, 2026 20:51 CEST

Status remains stable and we have worked through a hotfix to restore service to normal again. Maintenance window for this fix starts at 17.00 CET. Next update in conjunction with the maintenance window.

We have applied a hotfix to the service and as far as we have tested the functionality is fully restored. Changing status to "Operational". As we have had a prolonged period of issues we will now enter a stabilisation period where we very actively monitor the situation until we are certain all is under control. June 4, 2026 17:47 CEST

We have applied a hotfix to the service and as far as we have tested the functionality is fully restored. Changing status to "Operational". As we have had a prolonged period of issues we will now enter a stabilisation period where we very actively monitor the situation until we are certain all is under control.

We now deem the incident as resolved. Functionality is fully restored and the DBaaS service is in normal operational status. Back to current status Status History Report Issue 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] Yemen [+967] Zambia [+260] Zimbabwe [+263] Example: 201-555-1717 Close Subscribe Manage Subscript