|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical RE: Congestion peering C&W<->@home
This is probably more of an issue on @home's end, than C&Ws. Due to their current financial difficulties, @home has had to seriously slow down upgrades to it's peering infrastructure. I would not expect resolution of this, any time soon. - Daniel GOlding > -----Original Message----- > From: [email protected] [mailto:[email protected]]On Behalf Of > Seth M. Kusiak > Sent: Sunday, November 18, 2001 7:19 PM > To: German Martinez > Cc: [email protected] > Subject: Re: Congestion peering C&W<->@home > > > > Yes, I called CW support on this issue last week and I was told that they > are aware of the issue and that their 2nd and 3rd level techs are > on top of > it. They could not give me an ETA but said that the issue has > been going on > for 2-3 months. > > ~Seth > > German Martinez writes: > > > > > Hi, > > Have somebody notice some congestion between C&W and @home, > > > >>12 acr2-loopback.NewYork.cw.net (206.24.194.62) 153 ms 128 ms 149 ms > >> 13 * cable-and-wireless-peering.NewYork.cw.net > (206.24.193.242) 346 ms > >> 349 ms -------> peering congested. > >> 14 c1-pos4-0.cmdnnj1.home.net (24.7.65.229) 353 ms 340 ms * > > > > Is the same congestion all the time, it doesn't matter what time of the > > day. > > > > Any response, off/online will be highly appreciated. > > > > Thank you > > German > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > * THE DILBERT FUTURE * > > * Thriving on Stupidity in the 21st Century * > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > "Internet capacity will increase indefinitely > > to keep up with the egos of the people using it" > > > >
|