asn.dev

Observed topology

AS43500 WBD-AS Warner Bros. Discovery

Upstreams 11 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 6

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43500: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6422
AS174Cogent Communications, LLCTransitIPv4 IPv6200
AS6939Hurricane Electric LLCTransitIPv4 IPv6110
AS24482SG.GSHostingIPv4 IPv610
AS9002RETN LimitedUnclassifiedIPv68
AS7575Australian Academic and Research Network (AARNet)EducationIPv42
AS57463NetIX Communications JSCUnclassifiedIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS17639Converge ICT Solutions Inc.UnclassifiedIPv42
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv62
AS293ESnetUnclassifiedIPv41

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.

Transit

Downstream networks

inferred

Networks for which AS43500 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

16 shown

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6422
AS174Cogent Communications, LLCTransitIPv4 IPv6200
AS6939Hurricane Electric LLCTransitIPv4 IPv6110
AS24482SG.GSHostingIPv4 IPv610
AS9002RETN LimitedUnclassifiedIPv68
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS7575Australian Academic and Research Network (AARNet)EducationIPv42
AS17639Converge ICT Solutions Inc.UnclassifiedIPv42
AS57463NetIX Communications JSCUnclassifiedIPv42
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv62
AS293ESnetUnclassifiedIPv41

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.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS43500, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 6 exchanges across 3 countries and 3 regions.

ExchangeLocationTheir addressMember ports
IX.br (PTT.br) São PauloSão Paulo, Brazil187.16.217.2132,690
Coresite - Any2 WestLos Angeles, United States206.72.210.129344
Any2 CaliforniaLos Angeles, United States206.72.210.129321
Equinix Internet Exchange DallasDallas, United States206.223.119.34225
FL-IX - The Florida Internet Exchange / Community IX - FloridaMiami, United States206.41.108.33179
Budapest Internet ExchangeBudapest, Hungary193.188.137.67119

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

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

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

Exchange presence comes from a separate dataset: the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.