asn.dev

Observed topology

AS14543 SRT-ASN - SRT Communications, Inc.

Residential ARIN Cable/DSL/ISP

Upstreams 3 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 7
Adjacent (IPv6) 5
Upstream graph Who carries AS14543, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS14543 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS14543: 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
AS6461Zayo BandwidthTransitIPv4 IPv6394
AS3356Level 3 Parent, LLCTransitIPv4 IPv6304
AS2914NTT America, Inc.TransitIPv4 IPv6189

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS18780Reservation Telephone Coop.UnclassifiedIPv4 IPv6211
AS55215Trinity HealthUnclassifiedIPv471
AS55105NORTHWEST COMMUNICATIONS COOPERATIVEUnclassifiedIPv4 IPv620

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv6522
AS3356Level 3 Parent, LLCTransitIPv4 IPv6455
AS2914NTT America, Inc.TransitIPv4 IPv6216
AS18780Reservation Telephone Coop.UnclassifiedIPv4 IPv6211
AS55215Trinity HealthUnclassifiedIPv471
AS55105NORTHWEST COMMUNICATIONS COOPERATIVEUnclassifiedIPv4 IPv620
AS26794Dakota Carrier NetworkResidentialIPv44

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.