Revelation.com Provider is too slow. (AREV Specific)
At 27 OCT 1999 11:58:34AM CT Savell wrote:
I frequently have problems trying to log to the REVELATION web site. I did a:
tracert www.revelation.comand obtained the following report:
1 120 ms 126 ms 117 ms sdts11.znet.net 207.167.66.2522 125 ms 107 ms 122 ms sdir1-e1-2.znet.net 207.167.66.2543 138 ms 130 ms 109 ms 905.Hssi5-0.GW1.SDG1.ALTER.NET 137.39.132.294 112 ms 122 ms 140 ms 144.ATM3-0.XR2.LAX2.ALTER.NET146.188.249.70
5 120 ms 119 ms 116 ms 194.ATM1-0-0.BR1.LAX1.ALTER.NET146.188.248.205
6 535 ms 540 ms 499 ms core9-hssi5-0-0.Bloomington.cw.net206.157.77.5
7
7 558 ms 416 ms 316 ms corerouter2.Bloomington.cw.net204.70.9.148
8 329 ms 392 ms 532 ms xcore2.Boston.cw.net 204.70.150.739 420 ms 491 ms 467 ms revelation-technologies.Boston.cw.net166.63.38
.226
10 386 ms 425 ms 426 ms www.revelation.com 208.159.44.3
Times in the 400ms and higher range on a dialup account indicate that
that site is having some sort of problem (typically heavy traffic or a
down router). From this it looks as though cw.net is having
significant issues. I suggest that Revelation look into this and perhaps find another provider.
Anyone else having problems?
At 27 OCT 1999 01:09PM Victor Engel wrote:
I'm not seeing that at all from work or home (neither is dialup). Here are my results from work:
Tracing route to www.revelation.com 208.159.44.3
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 143.166.183.22 1 ms 1 ms 1 ms bt17k2-99.us.dell.com 143.166.99.33 3 ms 2 ms 2 ms starsky-in.us.dell.com 143.166.224.24 2 ms 2 ms 3 ms dell-gw2-fa000.us.dell.com 10.180.224.15 9 ms 9 ms 8 ms bordercore1-hssi6-0-1.Dallas.cw.net 166.48.78.56 9 ms 8 ms 7 ms corerouter2.Dallas.cw.net 204.70.9.1507 69 ms 69 ms 69 ms xcore2.Boston.cw.net 204.70.150.738 76 ms 76 ms 77 ms revelation-technologies.Boston.cw.net 166.63.38.226
9 75 ms 78 ms 75 ms www.revelation.com 208.159.44.3Trace complete.
Tracing route to www.revelation.com 208.159.44.3
over a maximum of 30 hops:
1 1 ms <10 ms 1 ms 143.166.183.22 1 ms 1 ms 1 ms bt17k2-99.us.dell.com 143.166.99.33 1 ms 1 ms 1 ms starsky-in.us.dell.com 143.166.224.24 3 ms 1 ms 2 ms dell-gw2-fa000.us.dell.com 10.180.224.15 9 ms 10 ms 9 ms bordercore1-hssi6-0-1.Dallas.cw.net 166.48.78.56 7 ms 8 ms 8 ms corerouter2.Dallas.cw.net 204.70.9.1507 70 ms 69 ms 68 ms xcore2.Boston.cw.net 204.70.150.738 76 ms 77 ms 76 ms revelation-technologies.Boston.cw.net 166.63.38.226
9 74 ms 75 ms 75 ms www.revelation.com 208.159.44.3Trace complete.
At 27 OCT 1999 03:26PM Steve Smith wrote:
Response times have been good to Australia, typically under 300 ms.
Using a public domain tracer at
http://dove.net.au/member/troute.html (close to me)
I typically reach this next node in 30 ms, not 105ms. I am on 56 kB modem.
5 Fddi1-0-1.lon6.Melbourne.telstra.net (139.130.49.81) 105.551 ms 222.869 ms 216.853 ms
6 Fddi0-0.lon5.Melbourne.telstra.net (139.130.239.231) 123.762 ms 86.801 ms 23.343 ms
7 borderx2-hssi3-0.Bloomington.cw.net (204.70.208.121) 368.063 ms 370.299 ms 413.647 ms
8 core1-fddi-1.Bloomington.cw.net (204.70.3.129) 315.713 ms 313.902 ms 313.793 ms
9 corerouter1.Bloomington.cw.net (204.70.9.147) 315.075 ms 321.151 ms 313.686 ms
10 xcore2.Boston.cw.net (204.70.150.73) 378.886 ms 378.230 ms 379.219 ms
11 revelation-technologies.Boston.cw.net (166.63.38.226) 389.107 ms 384.732 ms 385.430 ms
FWIW,
Steve
At 27 OCT 1999 07:20PM Warren wrote:
I can't run a tracert due to the firewall here, but compared to earlier this year when there was a definite bottle-neck response times are quite rapid.
I would suggest you contact your ISP and find out what MTU size they have their PPP connection set to, get a MTU tweaking utility and adjusting your DUN TCP/IP MTU setting to the same and re-running the tracert.
At 27 OCT 1999 07:27PM Warren wrote:
Try playing with the on-line demo these guys have: