asn.dev

Observed topology

AS199713 MLL-AS

Unclassified RIPE

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS199713: 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
AS174Cogent Communications, LLCTransitIPv4246
AS786Jisc Services LimitedEducationIPv4183
AS6461Zayo BandwidthTransitIPv4183
AS6939Hurricane Electric LLCTransitIPv4120
AS34549meerfarbig GmbH & Co. KGHostingIPv436
AS50304Blix Solutions ASUnclassifiedIPv424
AS3741Dimension DataUnclassifiedIPv412
AS12552GlobalConnect ABUnclassifiedIPv412
AS12779IT.Gate S.p.A.UnclassifiedIPv412
AS17639Converge ICT Solutions Inc.UnclassifiedIPv412

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49247East Sussex Fire AuthorityUnclassifiedIPv462
AS49728Herefordshire CouncilUnclassifiedIPv459
AS197370Nottinghamshire County CouncilUnclassifiedIPv459

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4273
AS786Jisc Services LimitedEducationIPv4245
AS6461Zayo BandwidthTransitIPv4220
AS6939Hurricane Electric LLCTransitIPv4140
AS49247East Sussex Fire AuthorityUnclassifiedIPv462
AS49728Herefordshire CouncilUnclassifiedIPv459
AS197370Nottinghamshire County CouncilUnclassifiedIPv459
AS34549meerfarbig GmbH & Co. KGHostingIPv442
AS50304Blix Solutions ASUnclassifiedIPv428
AS3741Dimension DataUnclassifiedIPv414

Provenance

Where this comes from

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