asn.dev

Observed topology

AS31747 BLACKROCK-FINANCIAL-MANAGEMENT-2 - BlackRock Financial Management, Inc.

Unclassified ARIN

Upstreams 10 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 0
Upstream graph Who carries AS31747, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS31747 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31747: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS32787Akamai Technologies, Inc.HostingIPv41,020
AS4637Telstra GlobalUnclassifiedIPv4153
AS3356Level 3 Parent, LLCTransitIPv4144
AS8220COLT Technology Services Group LimitedHostingIPv4144
AS701Verizon BusinessResidentialIPv499
AS2516KDDI CORPORATIONMobileIPv460
AS9255Singapore TelecomUnclassifiedIPv459
AS10021KVH Co.,LtdUnclassifiedIPv446
AS174Cogent Communications, LLCTransitIPv435
AS11351Charter Communications IncResidentialIPv431

Transit

Downstream networks

inferred

Networks for which AS31747 was observed as the last hop before the origin, meaning it appears to provide them transit.

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS31747 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS32787Akamai Technologies, Inc.HostingIPv41,020
AS4637Telstra GlobalUnclassifiedIPv4153
AS3356Level 3 Parent, LLCTransitIPv4144
AS8220COLT Technology Services Group LimitedHostingIPv4144
AS701Verizon BusinessResidentialIPv499
AS2516KDDI CORPORATIONMobileIPv460
AS9255Singapore TelecomUnclassifiedIPv459
AS10021KVH Co.,LtdUnclassifiedIPv446
AS174Cogent Communications, LLCTransitIPv435
AS11351Charter Communications IncResidentialIPv431

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-04 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.33M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.