Identified - Sub-sea cable system outage caused multiple carriers we used in Asia regions to have serious congestion and packet loss. We've disabled NTT temporarily.

Please don't hesitate to open a ticket if you have any questions. We can re-route destinations temporarily to solve latency or packet loss issue.
Dec 27, 06:08 UTC
Public API Operational
Cloud Servers Operational
Object Storage Operational
Block Storage Operational
Package Mirrors Operational
Authoritative DNS Operational
Recursive DNS Operational
DNS Updates Operational
Analytics Operational
SDN Controller Operational
Mail Queue Operational
Legacy Services Operational
SolusVM Master Operational
Metadata Service (Legacy) Operational
WHMCS (ZeptoVM) Operational
External Services Operational
Cloudflare CDN Operational
Mailgun Operational
Stripe API Operational
Datacenters Operational
Ashburn, VA, United States - (IAD01) Operational
Reston, VA, United States - (IAD03) Operational
Secaucus, NJ, United States - (EWR02) Operational
Kansas City, MO, United States - (MCI01) Operational
Seattle, WA, United States - (SEA02) Operational
Los Angeles, CA, United States - (LAX07) Operational
Montréal, QC, Canada - (MTL03) Operational
São Paulo, Brazil - (SAO03) Operational
Amsterdam, Netherlands - (AMS03) ? Operational
Amsterdam, Netherlands - (AMS04) ? Operational
Frankfurt, Germany - (FRA08) ? Operational
London, United Kingdom - (LHR06) ? Operational
London, United Kingdom - (LHR07) ? Operational
Madrid, Spain - (MAD02) Operational
Milan, Italy - (MIL01) Operational
Prague, Czech Republic - (PRG01) Operational
Sofia, Bulgaria - (SOF01) Operational
Stockholm, Sweden - (STO01) Operational
Oslo, Norway - (OSL01) Operational
Moscow, Russia - (MSK04) ? Operational
Saint Petersburg, Russia - (LED01) Operational
Khabarovsk, Russia - (KHV01) Operational
Tokyo, Japan - (NRT04) ? Operational
Hong Kong - (HKG12) ? Operational
Seoul, South Korea - (ICN05) Operational
Johannesburg, South Africa - (JNB01) Operational
Singapore - (SIN03) Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jan 25, 2022

No incidents reported today.

Jan 24, 2022

No incidents reported.

Jan 23, 2022
Resolved - This incident has been resolved.
Jan 23, 14:54 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 23, 14:33 UTC
Update - We're still working with our transit provider to investigate this issue.
Jan 23, 14:22 UTC
Investigating - We are currently investigating this issue.
Jan 23, 13:55 UTC
Resolved - This incident has been resolved.
Jan 23, 00:54 UTC
Investigating - We are currently investigating this issue.
Jan 22, 10:21 UTC
Jan 22, 2022
Resolved - This incident has been resolved.
Jan 22, 07:26 UTC
Investigating - We are currently investigating this issue.
Jan 22, 06:52 UTC
Jan 21, 2022

No incidents reported.

Jan 20, 2022

No incidents reported.

Jan 19, 2022
Resolved - This incident has been resolved.
Jan 19, 15:46 UTC
Investigating - We are currently investigating this issue.
Jan 19, 15:03 UTC
Jan 18, 2022

No incidents reported.

Jan 17, 2022

No incidents reported.

Jan 16, 2022

No incidents reported.

Jan 15, 2022
Resolved - This incident has been resolved.
Jan 15, 21:19 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 15, 21:03 UTC
Investigating - We are currently investigating this issue.
Jan 15, 20:56 UTC
Jan 14, 2022
Completed - The scheduled maintenance has been completed.
Jan 14, 23:24 UTC
Verifying - Verification is currently underway for the maintenance items.
Jan 14, 23:22 UTC
Update - Scheduled maintenance is still in progress. We will provide updates as necessary.
Jan 14, 22:27 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 14, 20:05 UTC
Scheduled - We want to announce planned migration in our service in Hong Kong. This migration carries an interruption of connectivity on servers of up to a maximum of 3 hours. If your servers are purchased after 1 Jan 2022, you won't be affected by the migration.
Jan 14, 18:07 UTC
Jan 13, 2022

No incidents reported.

Jan 12, 2022

No incidents reported.

Jan 11, 2022
Resolved - This incident has been resolved.
Jan 11, 10:29 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 11, 04:28 UTC
Investigating - We are currently investigating this issue.
Jan 11, 04:18 UTC