access to zope.com ? a bad router
Again today I couldn't access the zope.com website. The trace reveled: 1 1184 ms 109 ms 105 ms stan-m010.cybertours.com [208.153.18.2] 2 110 ms 110 ms 110 ms stan-r1.pivot.net [206.98.61.126] 3 115 ms 115 ms 109 ms prtl-r0-e3-0.cyberTours.com [206.98.60.253] 4 120 ms 120 ms 114 ms borderx1-hssi4-0.Boston.cw.net [204.70.179.109] 5 125 ms 129 ms 119 ms core-fddi-0.Boston.cw.net [204.70.2.33] 6 125 ms 120 ms * core4.WestOrange.cw.net [204.70.4.77] 7 129 ms 124 ms 125 ms sprint3-nap.WestOrange.cw.net [204.70.10.226] 8 * 125 ms 119 ms pnnj-01.core.exodus.net [192.157.69.25] 9 * * 135 ms dcr01-h10-0-0.jrcy01.exodus.net [209.1.169.209] 10 135 ms 130 ms 127 ms bbr01-p1-3.jrcy01.exodus.net [216.32.173.122] 11 130 ms 135 ms 131 ms bbr01-p5-0.hrnd01.exodus.net [209.185.249.214] 12 140 ms 124 ms 134 ms bbr02-p6-0.hrnd01.exodus.net [209.185.249.2] 13 220 ms 204 ms 205 ms bbr02-p0-1.irvn01.exodus.net [209.185.9.206] 14 205 ms 204 ms 205 ms dcr02-p0-0-0.irvn01.exodus.net [209.185.249.9] 15 210 ms 205 ms * rsm-ir-b-vl920.lan.exodus.net [209.67.128.102] 16 269 ms * * zope.org [209.67.167.110] 17 204 ms 205 ms * zope.org [209.67.167.110] 18 * 205 ms 204 ms zope.org [209.67.167.110] Is there a problem with an exodus.net router. Is exodus.net the zope ultimate provider? This is the third time this week. -bobo connor bob@rocnet.com
Exodus claims that they are aware of the problem and our in the process of upgrading the bandwidth to their various peering points. Same old story. They've requested that I send them traceroutes from the troubled connections. I figured we could have some fun with this, if the zope list is willing to help. If anybody thinks that the zope.org is running slow could you please e-mail a traceroute to traceroute@codeit.com. Thanks in advance for your help! On Fri, 9 Apr 1999, Robert OConnor wrote:
Again today I couldn't access the zope.com website. The trace reveled:
1 1184 ms 109 ms 105 ms stan-m010.cybertours.com [208.153.18.2] 2 110 ms 110 ms 110 ms stan-r1.pivot.net [206.98.61.126] 3 115 ms 115 ms 109 ms prtl-r0-e3-0.cyberTours.com [206.98.60.253] 4 120 ms 120 ms 114 ms borderx1-hssi4-0.Boston.cw.net [204.70.179.109]
5 125 ms 129 ms 119 ms core-fddi-0.Boston.cw.net [204.70.2.33] 6 125 ms 120 ms * core4.WestOrange.cw.net [204.70.4.77] 7 129 ms 124 ms 125 ms sprint3-nap.WestOrange.cw.net [204.70.10.226] 8 * 125 ms 119 ms pnnj-01.core.exodus.net [192.157.69.25] 9 * * 135 ms dcr01-h10-0-0.jrcy01.exodus.net [209.1.169.209]
10 135 ms 130 ms 127 ms bbr01-p1-3.jrcy01.exodus.net [216.32.173.122] 11 130 ms 135 ms 131 ms bbr01-p5-0.hrnd01.exodus.net [209.185.249.214] 12 140 ms 124 ms 134 ms bbr02-p6-0.hrnd01.exodus.net [209.185.249.2] 13 220 ms 204 ms 205 ms bbr02-p0-1.irvn01.exodus.net [209.185.9.206] 14 205 ms 204 ms 205 ms dcr02-p0-0-0.irvn01.exodus.net [209.185.249.9] 15 210 ms 205 ms * rsm-ir-b-vl920.lan.exodus.net [209.67.128.102] 16 269 ms * * zope.org [209.67.167.110] 17 204 ms 205 ms * zope.org [209.67.167.110] 18 * 205 ms 204 ms zope.org [209.67.167.110]
Is there a problem with an exodus.net router. Is exodus.net the zope ultimate provider?
This is the third time this week.
-bobo connor bob@rocnet.com
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
--------------------------------------------------- - Scott Robertson Phone: 714.972.2299 - - CodeIt Computing Fax: 714.972.2399 - - http://codeit.com - ---------------------------------------------------
On Fri, Apr 09, 1999 at 09:39:18AM -0700, Scott Robertson wrote:
Exodus claims that they are aware of the problem and our in the process of upgrading the bandwidth to their various peering points. Same old story. They've requested that I send them traceroutes from the troubled connections. I figured we could have some fun with this, if the zope list is willing to help. If anybody thinks that the zope.org is running slow could you please e-mail a traceroute to traceroute@codeit.com.
I don't usually admit to having worked for Sprintlink during the early days, but ... oh well, there you have it :-) Anyway, the point Michel is making is completely accurate, what a hosting company needs is private peering arrangements with SLAs that guarantee some accountability. When I was at Sprint we were VERY agressive in pursuing private peerings (ANS/UUNet/MCI at the time, everyone else was <1%) and making sure that they were at least sized reasonably. You can control these. MAE* is a joke, nothing more, it'd be like claiming you had a CIX connection in 1995, interesting perhaps, but not terribly useful for getting traffic somewhere. Chris -- | Christopher Petrilli ``Television is bubble-gum for | petrilli@amber.org the mind.''-Frank Lloyd Wright
participants (3)
-
Christopher Petrilli -
Robert OConnor -
Scott Robertson