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
New NL stock shortly!
Will update. I've got your email and PMs too. Sorry, just been busy. I'll reach out soon.
How soon is soon
God willing, within the next few hours. Hardware is up already.
Netherlands available now: https://incognet.io/kvm-vps
More US stock soon.
It seems like the cache hasn't been invalidated.
It's out of stocks but when I turn on VPN, in stock.
ctrl+shift+r or https://portal.incognet.io/store/amsterdam-netherlands-vps
Try again. Looks like the APAC region mirror didn't get updated. (Also Tor mirror fell out of sync, will fix in a moment).
Clearnet mirrors should be updated though. May need to hard refresh. I'll rethink our caching mechanism for pages that have frequent updates like stock.
Did you find a solution? In a previous lifetime I used Cultured Code but you don't strike me as an Apple type.
There's talk of early failure signs over at Mailbox. Might be an opportunity for competition coming up.
Any chance for 1776 offer?
MannDude got into the MannCave over the festive season, and struggling to get on top of the after party mode?
👀👀👀
@MannDude
@MannDude I admit being a bit worried about you by now. What's going on?
I don’t blame him for being busy
paging sweden
Since I know tickets are ignored, I'll post it here.
VM and management panel are both down. Attempts to perform any action show:
Also, from the network inspector, all GET requests to
state.jsonreturn{"success":false}.There is currently an outage which they are investigating I see an update has been posted here: https://portal.incognet.io/serverstatus.php
D'oh! I should have just checked network status!
Ya I opened a ticket instead of checking the status page
One of my servers was affected by the Stockholm hypervisor issue, and it seems to have been resolved now (at least for me).
ya my unit came back about 0600UTC plus a reboot an hour later.
downtime was ~11hrs.
didnt open a ticket, was clearly a bigger issue than my vm.
planning to sue etc.
Correct, had a hypervisor issue in Sweden. Please also tag me (@MannDude) on LET if requesting LET updates since it'll go to an inbox that gives me a phone notification as well.
If you already have a ticket open about it, I'll be adding some credit for the issue. If you don't, please open a ticket and I'll make sure you're credited.
Other updates while I'm here:
legal team has advised me to not accept credit as it may interfere with lawsuit sorry
#0217Y55Y7 opened
👀
If I have a lifetime plan, can I get an extra 256 MiB of RAM instead?
Seriously though, what would it cost to get an extra 256 (or 512)?
If VPS... yes!.
@MannDude tagging because you made me feel bad for not doing it last time so take that.
Looks like Sweden is still having (similar) issues?
Not critical but curious if there's anything you can share because nosy.
My vm emails me some stuff from syslog before it explodes, plus I see the reboots of course.
One of my VMs seemed (?) to be related to the issue, as it was using more resources than expected, but as I discussed in my ticket (#0217Y55Y7) to @MannDude, I have no idea why this would've been the case, because I was only hosting 2 small static sites with almost no traffic.
Suspending the VPS helped momentarily, but since the problem is back, I'm as lost as you are.
@MannDude My VPS (168.222.241.36) is down and shows "Suspended" in the dashboard, but not in the client area. I also received no email about this. It's just a Tor middle relay. What's happened?
100% CPU usage for a long period and 150%+ BW usage, though that auto-throttles but still isn't "unlimited".
I'll be back to my desk in a couple of hours. I remember that VM though since the host name was "Tor Middle" or something... was one of 3 that kept going to 100% CPU and causing triple digit hypervisor loads. I think the others just got a CPU throttle applied temporarily. Will review this all later. Was late and doing this was bette than letting a few VMs cause issues for the other couple dozen there.
Only POP I've seen this in has been SE.