This is also done with packages of 32 bites, if you increase this ( i do not know how big
the packages are that we send ) the drop will become bigger.

So make it "ping 211.43.149.199 -L 3000 -t" or something like that, and see if losses get
way bigger or just a little bid.
The -L is for the package size and the -T means it just keeps on pinging until you either
exit or press ctrl C

well i`ll usual fight with not much leg and this form uk mate ... we have one of the worse
internet connections ever .... so may some with ya router isn`t running to well

Hows the lag gowing after server maintaince?

Same here, you can se that my ping is 10-15 to the ISP, my pc is from year 2011 lol but i
also have lag on my notebook so, i also get a timeout!

From line 7-14 the lag starts

I've been having more crashes and lag spikes recently as well. No, it'S not my ISP and my
Laptop ain't from 2002 either.

**NF US Nebraska Server Trace By Hoplita**

Traceren van de route naar 211.43.149.199 via maximaal 30 hops

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 7 ms 7 ms 8 ms 10.239.96.1
3 8 ms 11 ms 6 ms 213.51.151.113
4 10 ms 9 ms 8 ms csw2-pc156.tilbu1.nb.home.nl [213.51.151.95]
5 12 ms 12 ms 12 ms asd-tr0409-cr101-ae5-0.core.as9143.net [213.51.1
58.154]
6 13 ms 13 ms 14 ms ae5.ams20.ip4.tinet.net [77.67.64.65]
7 180 ms 203 ms 170 ms xe-4-1-0.sjc12.ip4.tinet.net [89.149.186.205]
8 168 ms 169 ms 169 ms panther-express-gw.ip4.tinet.net [77.67.68.138]

9 211 ms 210 ms 211 ms 174.35.18.121
10 190 ms 198 ms 198 ms 174.35.18.74
11 187 ms * 185 ms 174.35.12.6
12 177 ms 180 ms 174 ms 174.35.13.246
13 185 ms 185 ms 185 ms 208.80.251.170
14 189 ms 189 ms 191 ms 211.43.149.199

De trace is voltooid.
**Gowing to test packet loss**

Pingen naar 211.43.149.199 met 32 bytes aan gegevens:
Antwoord van 211.43.149.199: bytes=32 tijd=190 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=198 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=188 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=187 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=190 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=189 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=191 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=189 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=190 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=189 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=191 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=190 ms TTL=107
Time-out bij opdracht.
Antwoord van 211.43.149.199: bytes=32 tijd=190 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=190 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=189 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=189 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=189 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=190 ms TTL=107
Antwoord van 211.43.149.199: bytes=32 tijd=190 ms TTL=107

Ping-statistieken voor 211.43.149.199:
Pakketten: verz .onden = 20, .ontvangen = 19, verloren = 1
(5% verlies).

No, i'm smart anough to tell you it's not my pc but the route that the connection takes,
to the server. it coud simple be that your connection goes trough other hops as mine.

No lagg here. Must be your PC.