TECHIEMEDIA

'Nuff said.

Also - if a router fails on YOUR ISP, that's not the hosts issue - thats your issue. During your traceroutes, you're seeing routes die on Level3 - ServerProvider doesn't have any bandwidth from Level3 - this is an issue with the BGP Peers along the way from princeton.edu - I ran traceroutes to all hosts you tried to attack from all of my carriers, and none of them had any issue.

Seriously, read a book before I have to school you some more

No, in the case it was denoting a latency since it continued to pass.

I love watching all the little hosts begging for the 1 meg customer. Giving the BW away for cost or below and tossing in a $2k server.........hahaha It's like the likewhoa biz model:1orglaugh

Didnt Cogent just buy the majority of Verios network:1orglaugh

It was still latency on Level3 - NOT Verio. Seriously man, save face and shut up now.

Servers have tax writeoff incentives, and can be built for way less than 2k (http://www.rackmountsetc.com) - bandwidth is dirt cheap from some providers - I also haven't seen any PR about Verio selling to Cogent, might have missed it tho.

Just sold their T1 assets. http://www.bizjournals.com/denver/st...9/daily42.html

probably small biz customers

if u know what the hell yur doing,
then these guys are a great host:

http://vaultnetworks.com

managed is pretty pricey,
but if u manage it yourself,
its fucking cheap!

just auto backup and get a remote boot.
that'll cover your ass..

So educate me Andrew. When pinging verio you wouldn't see line 12 as a problem.

tracing path from www.net.princeton.edu to 192.217.194.37 ...

traceroute to 192.217.194.37 (192.217.194.37), 30 hops max, 40 byte packets
1 gigagate1 (128.112.128.114) 0.462 ms 0.305 ms 0.290 ms
2 vgate1 (128.112.12.22) 0.353 ms 0.324 ms 0.318 ms
3 209.92.72.201 (209.92.72.201) 11.955 ms 9.735 ms 9.972 ms
4 165.113.8.66 (165.113.8.66) 19.277 ms 11.378 ms 10.214 ms
5 4.78.164.9 (4.78.164.9) 10.671 ms 7.740 ms 7.356 ms
6 ge-6-0-0.mp1.Philadelphia1.Level3.net (64.159.0.145) 5.308 ms 8.700 ms 9.818 ms
7 so-6-1-0.bbr2.NewYork1.Level3.net (209.247.8.66) 10.213 ms so-0-1-0.bbr1.NewYork1.Level3.net (64.159.1.41) 11.511 ms so-6-1-0.bbr2.NewYork1.Level3.net (209.247.8.66) 15.479 ms
8 ge-2-0.core2.NewYork1.Level3.net (4.68.97.9) 15.005 ms ge-5-2.core2.NewYork1.Level3.net (4.68.97.169) 11.191 ms ge-2-0.core2.NewYork1.Level3.net (4.68.97.9) 10.416 ms
9 oc12.Level3.nycmny01.us.bb.verio.net (209.244.160.150) 9.159 ms 15.552 ms 8.783 ms
10 p16-1-1-0.r20.nycmny01.us.bb.verio.net (129.250.2.36) 13.209 ms 10.889 ms 13.087 ms
11 p16-0-1-1.r20.mlpsca01.us.bb.verio.net (129.250.5.112) 98.321 ms 109.663 ms 106.321 ms
12 mg-1.a00.mlpsca01.us.da.verio.net (129.250.24.194) 99.883 ms * 79.424 ms
13 192.217.198.37 (192.217.198.37) 84.726 ms 82.892 ms 80.693 ms

50

ICMP responses can get queued giving the appearence of net latency. Download a file or pull up web pages to test speed.

I think you meant when tracerouting - but whatever - no I wouldn't take that as an issue, as I know carriers will asign a very low priority to non-essential packets (ie. ICMP). The star will represent a single packet timed out, which is quite possible consdering the numerous factors. You want to run a true test on packet delivery? Do an extended ping - I just ran one for a few minutes:

Ping statistics for 168.143.187.47:
Packets: Sent = 143, Received = 143, Lost = 0 (0% loss),

0% packet loss here, nothing to complain about on 0% packet loss.

You're telling that to the wrong person fucktard

But it only happens every 1 out of 3. If it a priority issue should you notice some latency on that hop each time?

Dooood - seriously, pick up a fucking book - I ain't tech support for your ass.

The priority is based on the amount of incoming packets at that time, and the current queue. If you can't already fucking tell, packet counts change every second. Christ you people drive me nuts

:glugglug