asn.dev

Observed topology

AS13188 TRIOLAN CONTENT DELIVERY NETWORK LTD

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS13188: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv647,567
AS35297Dataline LLCUnclassifiedIPv4 IPv621,449
AS174Cogent Communications, LLCTransitIPv4 IPv69,147
AS199995Omega Telecom LLCResidentialIPv48,657
AS9002RETN LimitedUnclassifiedIPv4 IPv66,936
AS35320Eurotranstelecom LtdUnclassifiedIPv4 IPv65,934
AS28917Fiord Networks, UABUnclassifiedIPv41,834
AS24482SG.GSHostingIPv4 IPv61,649
AS6849JSC "Ukrtelecom"ResidentialIPv41,379
AS3255LLC EKSINTECHUnclassifiedIPv41,198

All 19 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39422Oleksandr YaremenkoUnclassifiedIPv4199

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv647,567
AS35297Dataline LLCUnclassifiedIPv4 IPv621,449
AS174Cogent Communications, LLCTransitIPv4 IPv69,147
AS199995Omega Telecom LLCResidentialIPv48,657
AS9002RETN LimitedUnclassifiedIPv4 IPv66,936
AS35320Eurotranstelecom LtdUnclassifiedIPv4 IPv66,133
AS28917Fiord Networks, UABUnclassifiedIPv41,834
AS24482SG.GSHostingIPv4 IPv61,649
AS6849JSC "Ukrtelecom"ResidentialIPv41,379
AS3255LLC EKSINTECHUnclassifiedIPv41,198

All 20 adjacent →

Provenance

Where this comes from

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