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
Albania is back online for me
Correct. Everyone should be back online now - and compensation emails will go out shortly after we go through all our checks on our side and post-incident procedures.
Keep an eye on your email - all clients on Albania and MK with non-expired services that were ordered before 17:55 CEST 22-07-2026 will get an email with compensation details, post-incident report, etc shortly.
It's not complaining with the isos you have on there.
The ones that do it from helicopters are the ballsiest people in the world.
Hmm, it's still down for me and still gives the "Could not find VM node in Proxmox." error.
Server is zgkbhcvu.rscomputers-ks.com (195.144.24.78).
Yes, it went down again due to an exploding high-voltage power line and fire along fiber paths.
The first time, the cables were damaged and teams spent over 18 hours in the field clearing the debris and damage before repairing the cable. Again last night at around 10PM CEST, a high power line exploded in a region where our cables pass-through. Fire department worked until 5AM this morning (CEST) clearing the debris and making the site safe for workers to enter. 7AM (CEST) crews arrived back at the site to begin work on fixing the cable. It's now ~ 7:40AM CEST and we're awaiting response from ground crews once they've removed all the damaged cable and replaced it yet again. In the meantime, we've also already began looking for other options (different cable providers, different datacenters) in the area to see if there's any less effected by these storms so we can move or add cables - but for now, all we can do is wait the ground crews to fix the existing lines. This is a natural disaster of great magnitude - that has caused significant infrastructure damage, deaths, and property damage across the entire region.
We're expecting the main line to be repaired shortly - yet again. There's ~100m segment that is destroyed entirely in this blast and resulting fire.
We are actually provided with redundant fiber paths by our DF provider (2 fibers going different geographic routes) - however in the initial storm, both were broken entirely. The main line was repaired first yesterday - the backup lines were to be repaired today - however, before that could happen, the high-voltage lines exploded along the main path, causing the fire and resulting downtime. Once that's repaired and we're back online, we expect the teams will start to repair the backup line so the redundant paths are restored.
👍
It's funny how you're the privacy advocate around here moreso than most others, but NONE of us would post our own IP and hostnode like that.
Edit: oh, you meant the node was that IP, not your server. That makes more sense.
Yo do realize that tor relays are public with their ip?
What's the price of tea in China?
No, that is the server's IP. You can see a list of all my server's IPs here: https://metrics.torproject.org/rs.html#search/family:C79C7E957B045113F6633AB5DA17433F30E49920 (which I also link to in my signature).
There's no need for me to hide my server IPs because they aren't meant to be private. The only things private on any of my servers' storage are the SSH host keys and Tor's private keys. Everything else I could literally make public without issue.
If someone wanted to find out what my AVS ISP's North Macedonnia VPS's IP was, they could trivially look through my list of relays and pick the one with an MK IP on the right ASN and it'd be that one.