Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop

Categories

In this Discussion

Home › Offers
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.

Early BF Sale | 1.5GB and 4.5GB KVM VPS @0,97USD + much more + renewal credit + NETHERLANDS

1…1920222425

Comments

  • zuketzuket Member

    Any plan for restocking second $1.89 plan

  • HostSlickHostSlick 🚩 Host Rep Tag Suspended

    @zuket said:
    Any plan for restocking second $1.89 plan

    Hi

    No

  • ChrisJPChrisJP Member
    edited December 2024

    @HostSlick said:

    @slimbro said:

    thank for the upgrade

    Bro your Speedtest seems to use some Speedtest Server in Kansas. Maybe wrong choosen due to wrong Geo Data they have. Since The VPS is in NL you might get incorrect Test results :wink:

    My VPS was also in this IP range and I was getting forced to Kansas speedtest servers too. I submitted a correction to MaxMind (the IP database that Speedtest uses) on the weekend and it was accepted right away. Today Speedtest pulled the updated data and the speedtest cli now correctly selects an Amsterdam server to test against.

    But these latency spikes and packet loss...

       Speedtest by Ookla

      Server: Labixe Ltd - Amsterdam (id: 54151)
         ISP: ColocationX
Idle Latency:     0.84 ms   (jitter: 0.19ms, low: 0.65ms, high: 1.06ms)
    Download:  1651.15 Mbps (data used: 2.2 GB)
                  1.11 ms   (jitter: 11.85ms, low: 0.59ms, high: 442.21ms)
      Upload:   889.45 Mbps (data used: 1.5 GB)
                  2.18 ms   (jitter: 22.54ms, low: 0.52ms, high: 669.30ms)
 Packet Loss:    82.9%
  Result URL: https://www.speedtest.net/result/c/30549f2d-7a2c-4c16-bff8-fd7c6a3e91b0

    @bdl said:

    @xingxinghuisi said:

    @mmint said:
    Thanks @HostSlick for swift delivery. Great service. I'm happily configuring now.

    One question: in a putty console the communication seems a bit staggered. Same thing when using the noVNC. Every now and then there seems a delay of half a second or so. I don't have this with the VPS of another provider. Is this the network perhaps a bit crowded? Is it something I need to fix in the configuration?

    same

    Me too.

    Pinging test IP supplied from my VPS also shows jumps of up to 12-15ms so I guess there's network shenanigans at work. May calm down when the new users stop YABSing their services ;)

    PING 193.142.146.1 (193.142.146.1) 56(84) bytes of data.
64 bytes from 193.142.146.1: icmp_seq=1 ttl=64 time=0.731 ms
64 bytes from 193.142.146.1: icmp_seq=2 ttl=64 time=0.608 ms
64 bytes from 193.142.146.1: icmp_seq=3 ttl=64 time=0.657 ms
64 bytes from 193.142.146.1: icmp_seq=4 ttl=64 time=0.928 ms
64 bytes from 193.142.146.1: icmp_seq=5 ttl=64 time=0.860 ms
64 bytes from 193.142.146.1: icmp_seq=6 ttl=64 time=0.695 ms
64 bytes from 193.142.146.1: icmp_seq=7 ttl=64 time=0.610 ms
64 bytes from 193.142.146.1: icmp_seq=8 ttl=64 time=0.926 ms
64 bytes from 193.142.146.1: icmp_seq=9 ttl=64 time=0.609 ms
64 bytes from 193.142.146.1: icmp_seq=10 ttl=64 time=0.736 ms
64 bytes from 193.142.146.1: icmp_seq=11 ttl=64 time=0.871 ms
64 bytes from 193.142.146.1: icmp_seq=12 ttl=64 time=0.784 ms
64 bytes from 193.142.146.1: icmp_seq=13 ttl=64 time=0.685 ms
64 bytes from 193.142.146.1: icmp_seq=14 ttl=64 time=0.766 ms
64 bytes from 193.142.146.1: icmp_seq=15 ttl=64 time=0.854 ms
64 bytes from 193.142.146.1: icmp_seq=16 ttl=64 time=0.828 ms
64 bytes from 193.142.146.1: icmp_seq=17 ttl=64 time=0.531 ms
64 bytes from 193.142.146.1: icmp_seq=18 ttl=64 time=0.844 ms
64 bytes from 193.142.146.1: icmp_seq=19 ttl=64 time=1.02 ms
64 bytes from 193.142.146.1: icmp_seq=20 ttl=64 time=0.782 ms
64 bytes from 193.142.146.1: icmp_seq=21 ttl=64 time=0.734 ms
64 bytes from 193.142.146.1: icmp_seq=22 ttl=64 time=0.869 ms
64 bytes from 193.142.146.1: icmp_seq=23 ttl=64 time=0.742 ms
64 bytes from 193.142.146.1: icmp_seq=24 ttl=64 time=15.4 ms
64 bytes from 193.142.146.1: icmp_seq=25 ttl=64 time=1.54 ms
64 bytes from 193.142.146.1: icmp_seq=26 ttl=64 time=2.02 ms
64 bytes from 193.142.146.1: icmp_seq=27 ttl=64 time=0.950 ms
64 bytes from 193.142.146.1: icmp_seq=28 ttl=64 time=1.72 ms
64 bytes from 193.142.146.1: icmp_seq=29 ttl=64 time=1.44 ms
64 bytes from 193.142.146.1: icmp_seq=30 ttl=64 time=2.07 ms
64 bytes from 193.142.146.1: icmp_seq=31 ttl=64 time=0.937 ms
64 bytes from 193.142.146.1: icmp_seq=32 ttl=64 time=2.95 ms
64 bytes from 193.142.146.1: icmp_seq=33 ttl=64 time=12.7 ms
64 bytes from 193.142.146.1: icmp_seq=34 ttl=64 time=0.745 ms
64 bytes from 193.142.146.1: icmp_seq=35 ttl=64 time=0.625 ms
64 bytes from 193.142.146.1: icmp_seq=36 ttl=64 time=1.03 ms
64 bytes from 193.142.146.1: icmp_seq=37 ttl=64 time=0.671 ms
64 bytes from 193.142.146.1: icmp_seq=38 ttl=64 time=0.506 ms
64 bytes from 193.142.146.1: icmp_seq=39 ttl=64 time=0.670 ms

    Almost 10 days on and this is still an issue for me, how about you guys? Very noticeable when typing commands. Ran YABS and all iperf3 tests just said "busy".

    One positive note is I see IPv6 has been fixed now even though the ticket is still open. But I feel like there's other network issues based on the above.

  • SkelterSkelter Member
    edited December 2024

    I bought on the 29th December, forgot to post request for extra goodies (Its still pending, so i hope its not a problem):

    Invoice #2024-11-29-738
    Order Number: 5270531759

    Double Port+Bandwidth +1CORE

    Thanked by 1bdl
  • bdlbdl Member

    @ChrisJP said:
    Almost 10 days on and this is still an issue for me, how about you guys? Very noticeable when typing commands. Ran YABS and all iperf3 tests just said "busy".

    I still notice it sometimes. I can confirm my GeoIP is now working properly (even though I was just selecting a server manually with speedtest flags in the past) and I'm receiving speeds as advertised.

    Ping is still jumping around, with higher and more frequent latency than before. Test just now:

    PING 193.142.146.1 (193.142.146.1) 56(84) bytes of data.
    64 bytes from 193.142.146.1: icmp_seq=1 ttl=64 time=0.776 ms
    64 bytes from 193.142.146.1: icmp_seq=2 ttl=64 time=0.611 ms
    64 bytes from 193.142.146.1: icmp_seq=3 ttl=64 time=0.633 ms
    64 bytes from 193.142.146.1: icmp_seq=4 ttl=64 time=0.964 ms
    64 bytes from 193.142.146.1: icmp_seq=7 ttl=64 time=8.85 ms
    64 bytes from 193.142.146.1: icmp_seq=8 ttl=64 time=0.592 ms
    64 bytes from 193.142.146.1: icmp_seq=9 ttl=64 time=1.07 ms
    64 bytes from 193.142.146.1: icmp_seq=10 ttl=64 time=21.4 ms
    64 bytes from 193.142.146.1: icmp_seq=12 ttl=64 time=15.7 ms
    64 bytes from 193.142.146.1: icmp_seq=13 ttl=64 time=0.865 ms
    64 bytes from 193.142.146.1: icmp_seq=14 ttl=64 time=0.770 ms
    64 bytes from 193.142.146.1: icmp_seq=15 ttl=64 time=0.827 ms
    64 bytes from 193.142.146.1: icmp_seq=16 ttl=64 time=0.572 ms
    64 bytes from 193.142.146.1: icmp_seq=17 ttl=64 time=0.865 ms
    64 bytes from 193.142.146.1: icmp_seq=18 ttl=64 time=0.691 ms
    64 bytes from 193.142.146.1: icmp_seq=19 ttl=64 time=0.857 ms
    64 bytes from 193.142.146.1: icmp_seq=20 ttl=64 time=0.689 ms
    64 bytes from 193.142.146.1: icmp_seq=21 ttl=64 time=0.892 ms
    64 bytes from 193.142.146.1: icmp_seq=22 ttl=64 time=1.65 ms
    64 bytes from 193.142.146.1: icmp_seq=23 ttl=64 time=1.30 ms
    64 bytes from 193.142.146.1: icmp_seq=24 ttl=64 time=1.09 ms
    64 bytes from 193.142.146.1: icmp_seq=26 ttl=64 time=118 ms
    64 bytes from 193.142.146.1: icmp_seq=27 ttl=64 time=21.4 ms
    64 bytes from 193.142.146.1: icmp_seq=28 ttl=64 time=31.6 ms
    64 bytes from 193.142.146.1: icmp_seq=31 ttl=64 time=6.16 ms
    64 bytes from 193.142.146.1: icmp_seq=33 ttl=64 time=11.0 ms
    64 bytes from 193.142.146.1: icmp_seq=34 ttl=64 time=8.45 ms
    64 bytes from 193.142.146.1: icmp_seq=35 ttl=64 time=1.46 ms
    64 bytes from 193.142.146.1: icmp_seq=36 ttl=64 time=0.634 ms
    64 bytes from 193.142.146.1: icmp_seq=37 ttl=64 time=0.737 ms
    64 bytes from 193.142.146.1: icmp_seq=38 ttl=64 time=0.705 ms
    64 bytes from 193.142.146.1: icmp_seq=39 ttl=64 time=0.790 ms
    64 bytes from 193.142.146.1: icmp_seq=40 ttl=64 time=22.8 ms
    64 bytes from 193.142.146.1: icmp_seq=41 ttl=64 time=1.05 ms
    64 bytes from 193.142.146.1: icmp_seq=42 ttl=64 time=0.685 ms
    64 bytes from 193.142.146.1: icmp_seq=43 ttl=64 time=13.9 ms
    64 bytes from 193.142.146.1: icmp_seq=44 ttl=64 time=0.699 ms
    64 bytes from 193.142.146.1: icmp_seq=45 ttl=64 time=0.856 ms
    64 bytes from 193.142.146.1: icmp_seq=46 ttl=64 time=18.9 ms
    64 bytes from 193.142.146.1: icmp_seq=47 ttl=64 time=0.674 ms
    64 bytes from 193.142.146.1: icmp_seq=48 ttl=64 time=0.938 ms
    64 bytes from 193.142.146.1: icmp_seq=49 ttl=64 time=0.636 ms
    64 bytes from 193.142.146.1: icmp_seq=50 ttl=64 time=0.928 ms
    64 bytes from 193.142.146.1: icmp_seq=51 ttl=64 time=92.6 ms
    64 bytes from 193.142.146.1: icmp_seq=52 ttl=64 time=0.937 ms
    64 bytes from 193.142.146.1: icmp_seq=53 ttl=64 time=0.617 ms
    64 bytes from 193.142.146.1: icmp_seq=54 ttl=64 time=0.651 ms

  • tenperatenpera Member

    all vms are down now.

  • keonkeon Member

    @tenpera said:
    all vms are down now.

    Yes mine is down as well...

    Thanked by 1emg88
  • WoooWooo Member

    @keon said:

    @tenpera said:
    all vms are down now.

    Yes mine is down as well...

    +1

  • cybertechcybertech Member
    edited December 2024

    seems to be whole thing down. either network or power

    sleepless night for the boss i guess

  • mmmxnrsmmmxnrs Member

    @tenpera said:
    all vms are down now.

    Dedicated Server same thing, another long downtime

  • mmmxnrsmmmxnrs Member

    @cybertech said:
    seems to be whole thing down. either network or power

    sleepless night for the boss i guess

    I’m worried that he’s already asleep, and no one can notify him, which would be bad. The issue occurred shortly after his last active time.

  • cybertechcybertech Member

    @mmmxnrs said:

    @cybertech said:
    seems to be whole thing down. either network or power

    sleepless night for the boss i guess

    I’m worried that he’s already asleep, and no one can notify him, which would be bad. The issue occurred shortly after his last active time.

    then you should go to sleep too

  • HOSTCAYHOSTCAY Member, Host Rep

    @mmmxnrs said:

    @cybertech said:
    seems to be whole thing down. either network or power

    sleepless night for the boss i guess

    I’m worried that he’s already asleep, and no one can notify him, which would be bad. The issue occurred shortly after his last active time.

    He is asleep.

  • kv1108kv1108 Member

    Outage 🤓

  • cybertechcybertech Member

    waking up soon.

  • ManuelMManuelM Member

    VPS down 🥲

  • OhJohnOhJohn Member

    Yupp, network down since about 8 hours.

  • CaztielCaztiel Member
    edited December 2024

    I believe he has a team working around in his absence. So they should have taken care of it. Unless if he is a one man army ?

  • adef_1adef_1 Member

    It feels like a oneman team, where tasks like adding IPv6 have to be postponed to an uncertain schedule.

  • mmmxnrsmmmxnrs Member

    Oh, he appeared half an hour ago. However, the problem still persists. It seems that this malfunction is not that easy to resolve.

  • bitarchitectbitarchitect Member

    It's working now...

  • adjayaadjaya Member

    My complaint via ticket has not been responded to. My blackfriday hosting, which is as old as corn, is gone and can't be accessed. 😰

  • keonkeon Member

    My VPS seems to be up now

  • mmmxnrsmmmxnrs Member

    I'm not sure about the VPS, but for Dedicated Servers, this is the longest downtime in the past two years, a record-breaking 9 hours.

  • cybertechcybertech Member

    show's over guys

    the router just took a nap after BFCM

  • coldcold Member

    @cybertech said:
    show's over guys

    the router just took a nap after BFCM

    money are cashed, so it can rest now for a few more hours

  • HostSlickHostSlick 🚩 Host Rep Tag Suspended

    hello,

    there was a problem with the Router Chassis - line cards going offline and not becoming online anymore after

    We are very sorry for that issue, it has been now fixed. We where working hard to investigate cause last hours.

    All is now fixed, dont worry.

    thanks

    Thanked by 2bitarchitect bdl
  • coldcold Member

    @HostSlick said:

    hello,

    there was a problem with the Router Chassis - line cards going offline and not becoming online anymore after

    We are very sorry for that issue, it has been now fixed. We where working hard to investigate cause last hours.

    All is now fixed, dont worry.

    thanks

    we're not worried, we eagerly wait for the new crash, in 2 to 3 weeks.

    thanks for a fast fix

  • loayloay Member

    @cold said: we're not worried, we eagerly wait for the new crash, in 2 to 3 weeks.

    :D

    Their service is amazing when it works, but I’m really disappointed by the recent downtimes, failing server HDDs, and IP changes. I hope things improve for them and they don’t end up deadpooling, though it’s starting to feel that way.

  • HostSlickHostSlick 🚩 Host Rep Tag Suspended

    @loay said:

    @cold said: we're not worried, we eagerly wait for the new crash, in 2 to 3 weeks.

    :D

    Their service is amazing when it works, but I’m really disappointed by the recent downtimes, failing server HDDs, and IP changes. I hope things improve for them and they don’t end up deadpooling, though it’s starting to feel that way.

    Yes and no Deadpool no

This discussion has been closed.