New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
It’s now alwyzoff
Can confirm. Virtual and storage server are down.
edited: it is now up, 40 minutes downtime.
Now it looks like they are back. As they were lost by bgp the servers were not rebooted
Outage was about 35-40 minutes
@alwyzon
https://www.alwyzon.com/en/status
Sorry to all whose server has experienced downtime during todays incident. As of now, or more specifically since 14:24 (UTC), all services should be reachable again.
At 13:42 (UTC), one of the two edge routers (edge2.vie) got into a yet to be further investigated state that caused all external traffic to be dropped. Such an incident on its own should not cause any downtime. The failover plan would be to route all traffic through the other router, but that’s not what happened and has let to the downtime you just experienced. For now, the potentially defective router has thus been taken offline, and the log files are used to reconstruct what exactly has happened.
As it has been the most frequently asked question via the support desk: no, you do not need to fear about your data. All servers should have been running through the entire downtime, so there is likely no need for manual intervention through customers at all. If your server has been online before, your server will likely be reachable again already.
Further details will be provided on alwyzon.com/status once available.
Can we receive some photos of faulty hardware?
Pervert.
But yes, as a fellow serverporn pervert... Photos would be cool.
The photos won't catch the smoke that already escaped.
Looking at their Status Page, they're rarlyoff, a synonym of alwyzon.
@alwyzon a suggestion: the status page was inaccessible during the outage, why not host it elsewhere to make it more resilient to such incidents?