Philip Smith's Internet Development Site

User Tools

Site Tools

Trace:
peering-toolbox:the_peering_database

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
peering-toolbox:the_peering_database [2022/08/26 07:17] – [Creating a PeeringDB Entry] philippeering-toolbox:the_peering_database [2023/04/30 05:45] (current) – [Background] philip
Line 13: Line 13:
 In the early Internet (of the 1990s) there were few network operators and interconnect points around the world that interconnections were relatively straightforward to seek out and implement (in the author's experience anyway). In March 1999 there were 4640 ASNs in the Internet with only 800 providing transit. This compares with today's total exceeding 73000 ASNs and over 10000 ASNs providing transit, never mind that almost every country in the world now has at least one Internet Exchange Point if not a datacentre facilitating commercial interconnects. In the early Internet (of the 1990s) there were few network operators and interconnect points around the world that interconnections were relatively straightforward to seek out and implement (in the author's experience anyway). In March 1999 there were 4640 ASNs in the Internet with only 800 providing transit. This compares with today's total exceeding 73000 ASNs and over 10000 ASNs providing transit, never mind that almost every country in the world now has at least one Internet Exchange Point if not a datacentre facilitating commercial interconnects.
  
-In the 1990s establishing new interconnects by attending in major Internet operations meetings (NANOG, RIPE, AfNOG, APRICOT and so on), with network information passed on by word of mouth or email or even by letter!+In the 1990s, establishing new interconnects was achieved by attending major Internet operations meetings (NANOG, RIPE, AfNOG, APRICOT and so on), with network information passed on by word of mouth or email or even by letter!
  
 With the rapid growth of the Internet in the late 1990s and early 2000s, there needed to be a more scalable way for a Network Operator to get their "peering information" out to the global Internet operations community. And hence the PeeringDB was born. With the rapid growth of the Internet in the late 1990s and early 2000s, there needed to be a more scalable way for a Network Operator to get their "peering information" out to the global Internet operations community. And hence the PeeringDB was born.
Line 33: Line 33:
 This one shows the Public peering and Private peering facilities AWS is present at. So a potential peer can check which locations they share with AWS, and then contact them about peering. The page for AWS contains data about number of prefixes, traffic ratios, etc, plus the IP addressing used at the various public Internet connect points. All this is designed to make it easier for prospective peers to assess and reach out to AWS for peering. This one shows the Public peering and Private peering facilities AWS is present at. So a potential peer can check which locations they share with AWS, and then contact them about peering. The page for AWS contains data about number of prefixes, traffic ratios, etc, plus the IP addressing used at the various public Internet connect points. All this is designed to make it easier for prospective peers to assess and reach out to AWS for peering.
  
-And the final example shows Aerelion (formerly Telia Carrier), the operator of AS1299, one of the international transit carriers serving the global Internet:+And the final example shows Arelion, the operator of AS1299, one of the international transit carriers serving the global Internet:
  
 {{:peering-toolbox:peeringdb-arelion.png?500|}} {{:peering-toolbox:peeringdb-arelion.png?500|}}
peering-toolbox/the_peering_database.1661498243.txt.gz · Last modified: by philip