Karl,
Thanks for the reply.
Quote:
Originally Posted by KarlZimmer
You've been approved for peering with Google?.
|
Not yet, I believe we'll reach the 100 Mbit threshold by the time we spin up the data center. At this point, I've only broached the peering question with Yahoo who responded with a thumbs up. This is new territory for me and Google is an important network for us so I'd like to start with someone else and then approach Google later.
According to Google's peering DB entry, the 100 Mbit level is a threshold for private or direct peering. Below that level, it appears you may peer via the route server:
Liberal peering policy subject to certain technical, commercial and legal requirements:
- Maintain a publicly routable ASN
- publicly routable address space (at least one /24)
- ASN record completed in PeeringDB
- 24x7 NOC contact capable of resolving BGP routing issues
- Fault management escalation list
- Presence at one or more of the IXes or accessible colocation facilities
Peering Traffic Requirements (IPv4):
+ Peers in North America or Western Europe with less than 100Mbps peak of Google traffic may peer via route servers at participating IXes.
+ Peers with more than 100Mbps peak of Google traffic may peer via a bilateral BGP session over an IX.
Google represents 2% of our inbound and 18% of our outbound traffic. If I've got the peering figured out wrong, it changes things for us so please let me know.
I realize our numbers are small and that port fees are not free. We'd probably be more in the 2-2.5 Gbit peak territory before any peering would be initiated. It still might not save us money but we're looking at it more strategically by choosing a data center that could support the option.
As for the deal, it came from MosaicNetworx described to me as a CLEC and bandwidth aggregator/wholesaler. They put us in touch with Equinix.
Thanks again.