I've heard rumors lately that on occassion the server has been slow to respond. I did a
trace and discovered the problem is in something known as the verio network and not with our server. Verio, as far as I'm concerned, should be shut down completely - nothing but a good for nothing bunch of layabouts. I've encountered them many times and every single one of them was for slow traffic. My condolences if your connection forces you through their wires.
Code:
TraceRoute to 207.36.86.166 [cownap.com]
Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 66.98.244.1 gphou-66-98-244-1.ev1.net
2 0 2 0 66.98.241.4 gphou-66-98-241-4.ev1.net
3 0 0 0 66.98.240.5 gphou-66-98-240-5.ev1.net
4 1 1 1 129.250.10.189 ge-2-0-0.r02.hstntx01.us.bb.verio.net
5 17 6 6 129.250.5.40 p16-1-0-3.r20.dllstx09.us.bb.verio.net
6 Timed out Timed out Timed out -
7 Timed out Timed out Timed out -
8 Timed out Timed out Timed out -
9 43 43 43 130.94.195.118 ge-4-2.a00.miamfl02.us.ce.verio.net
10 50 49 50 69.25.0.78 border6.pc2.bbnet2.mia003.pnap.net
11 44 44 44 69.25.48.6 affinityint-3.border6.mia003.pnap.net
12 45 45 45 216.219.251.2 ftl-core1b-v5.valueweb.com
13 45 45 44 207.36.86.166 207-36-86-166.ptr.primarydns.com
Trace complete
Bit o history.
- Interspeed was on verio - lasted a week and a half
- Communitech was taken over by verio - end of karf.net
- Rhino was transferred onto verio (in a misguided attempt to solve internal networking issues) - and then they stole the name.
I'm not saying we have anything to worry about (we are are NOT on the verio network) but as long as traffic gets routed through verio (and it's hard to avoid sometimes) then temporary interruptions can be expected.
