C&W Peering Problem?

I was wondering when this issue was going to be brought up. C&W
dropped peering with several backbones. I will bet the problems
started about a week ago.

Probably because they didn't meet the new C&W peering requirements.

They sent me a link to their peering requirements the other week when I
asked. Basically, to peer you have to have an OC48 backbone with
redundantly connected nodes in 9 regions of the USA (according to their
definition of regions), peering at 4 diverse locations, with a minimum of
45Mbit/s of traffic at each location.

Interestingly, C&W's network map doesn't show PoP's in all of their 9
regions.

Simon

Does anyone know who was dropped? I have been having strange connectivity
problems between my network on the C&W network and my datacenter which is on
GlobalCenter's net. No one can tell me what is going on, but maybe this has
something to do with it.

Jason Lewis
http://www.packetnexus.com
It's not secure "Because they told me it was secure". The people at the
other end of the link know less about security than you do. And that's
scary.

It wouldn't suprise me if C&W dropped GlobalCenter as a peering partner,
given GC's focus on datacenters and web/server farms generating mostly
"push" traffic - I didn't see this as an explicit requirement, but less
clueful backbones (Genuity, PSI, and now C&W) do tend to drop peering
sessions with other backbones that push far more traffic than they pull.

BTW, I just noticed that the Exodus/GC merger went through (at least,
www.globalcenter.com brings up Exodus's front page). When did this happen?

-C

I didn't see this as an explicit
requirement, but less
clueful backbones (Genuity, PSI, and now C&W) do tend
to drop peering
sessions with other backbones that push far more
traffic than they pull.

Read section IV of their policy again:

                                       IV. Traffic Requirements

                                            A. Each peering
connection speed shall be at least 155 Mbps.

                                            B. The traffic volume
at each peering connection shall be at least 45
                                            Mbps.

                                            C. The aggregated
traffic ratio shall not exceed a ratio of 2 : 1

                                            D. Traffic volumes
shall be measured in either direction, inbound or
                                            outbound, whichever
is higher, on a weekly aggregated average
                                            basis over all the
points where the parties exchange traffic

Point C says 2:1, but D says they don't care in which direction
its in, it just has to be balanced.

  -Scott

Exodus bought Global Center. The web hosting side of Global Crossing.
Global Center did not have a network. Global Crossing does.

Hope that helps...