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.
Online.NET Packet loss
DennisdeWit
Member
Just wondering: does anyone having a Dedicated Server at Online.NET experience packet loss the last two days? I can't stream without buffering.
So I ran a ping test to see if there's a package loss. Indeed, there is. Every 10th packet is lost, which means a packet loss of almost 10 percent. I already e-mailed their support, but I'm wondering wether I'm the only one.
Comments
I've never lost a package from online.net
It's happening since 2 days.
64 bytes from 212.83.128.61: icmp_seq=20 ttl=53 time=49.233 ms 64 bytes from 212.83.128.61: icmp_seq=21 ttl=53 time=51.176 ms Request timeout for icmp_seq 22 64 bytes from 212.83.128.61: icmp_seq=23 ttl=53 time=49.107 ms 64 bytes from 212.83.128.61: icmp_seq=24 ttl=53 time=44.402 ms 64 bytes from 212.83.128.61: icmp_seq=25 ttl=53 time=47.965 ms 64 bytes from 212.83.128.61: icmp_seq=26 ttl=53 time=43.831 ms 64 bytes from 212.83.128.61: icmp_seq=27 ttl=53 time=40.019 ms 64 bytes from 212.83.128.61: icmp_seq=28 ttl=53 time=52.144 ms 64 bytes from 212.83.128.61: icmp_seq=29 ttl=53 time=44.658 ms 64 bytes from 212.83.128.61: icmp_seq=30 ttl=53 time=52.368 ms 64 bytes from 212.83.128.61: icmp_seq=31 ttl=53 time=49.032 ms Request timeout for icmp_seq 32 64 bytes from 212.83.128.61: icmp_seq=33 ttl=53 time=45.558 ms 64 bytes from 212.83.128.61: icmp_seq=34 ttl=53 time=44.449 ms 64 bytes from 212.83.128.61: icmp_seq=35 ttl=53 time=44.483 ms 64 bytes from 212.83.128.61: icmp_seq=36 ttl=53 time=42.492 ms 64 bytes from 212.83.128.61: icmp_seq=37 ttl=53 time=44.795 ms 64 bytes from 212.83.128.61: icmp_seq=38 ttl=53 time=47.207 ms 64 bytes from 212.83.128.61: icmp_seq=39 ttl=53 time=45.788 ms Request timeout for icmp_seq 40 64 bytes from 212.83.128.61: icmp_seq=41 ttl=53 time=45.446 ms 64 bytes from 212.83.128.61: icmp_seq=42 ttl=53 time=44.622 ms 64 bytes from 212.83.128.61: icmp_seq=43 ttl=53 time=41.407 msI was being sarcastic. It's packet not package :P
Fixed!
@DennisdeWit run
for 100 iterations or more, that way you can see where the packet loss starts.
Looks like there's something broken in my nodeserver, according to the loss on 88.191.1.86 (which is my node IP).
I know no one has the time in this busy world, but I said 100 and you posted just 4, this is not nearly as useful.
Okay, here it is:
http://pastebin.com/JQdWmwMW
@dennisdewit how did you get OSX Mavericks?
Apple's Devcenter. Where else?