How do we calculate Down/Upstreams?

BGP itself has no direct way to encode the relationship between two networks. So bgp.tools has to do an educated guess to figure this out.

To do this. Let’s look at a single prefix.

ASN Path graph

bgp.tools displays the upstream list to look like this.

ASN Path graph

In the background, bgp.tools simply sees paths like:

PREFIX_AS_PATH: [[4777 2516 1299 3170 206924]]
PREFIX_AS_PATH: [[198290 2914 44684 206924]]
PREFIX_AS_PATH: [[41157 3257 1299 3170 206924]]
PREFIX_AS_PATH: [[20080 2914 3170 206924]]

To simplify, bgp.tools considers any ASN in the path for a prefix that contains a tier 1 to be in a upstreaming relationship. For example:

PREFIX_AS_PATH: [[198290 2914 44684 206924]]

In this case we see that 2914 (NTT, a ASN that bgp.tools considers to be a tier 1) connects to 44684 (Mythic) that then connects to our originator 206924. Meaning that bgp.tools will see 44684 as a upstream for 206924.

These relationships are also ported backwards to establish as providers downstreams.

Any relationship between two ASNs seen on the path are shown as peers on the site. Just because two providers are peering with each other does not mean that bgp.tools can see this. bgp.tools needs to be able to see the routing table inside that ASN (or one of it’s downstreams) to be able to see this.

The list of ASN’s that bgp.tools considers to be Tier 1’s are:

ASN Name
6762 Sparkle
12956 Telefonica
2914 NTT
3356 Lumen
6453 TATA
701 Verizon
6461 Zayo
3257 GTT
1299 Telia
3491 PCCW
7018 AT&T
3320 DTAG
5511 Orange
6830 Liberty Global
174 Cogent
6939 HE (IPv6 Only)

Route server upstreaming

In addition to a route being seen via a Tier 1, any path that is sent to a IXP route server (that bgp.tools has a feed from) is considered to be a upstreaming relationship.

If you want to help coverage, please email the contact address at the bottom of this site!