asn.dev

Observed topology

AS38949 TRESTEL-

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38949: 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 IPv6180
AS174Cogent Communications, LLCTransitIPv4 IPv644
AS24482SG.GSHostingIPv4 IPv64
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv64
AS3303Swisscom (Schweiz) AGResidentialIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS34820DELTA ONLINE spol. s r.o.ResidentialIPv4355
AS204384LLC "OTT UKRAINE"HostingIPv4244
AS61335PE Denis PodolskiiUnclassifiedIPv4 IPv6152
AS206804Realcloud OUUnclassifiedIPv4132
AS29531VM Telecom, s.r.o.UnclassifiedIPv4107
AS60585SITEL-VSAT sroUnclassifiedIPv4 IPv6103
AS48473Towercom a.s.UnclassifiedIPv432
AS60890CentralNic LtdUnclassifiedIPv61

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,156
AS34820DELTA ONLINE spol. s r.o.ResidentialIPv4484
AS174Cogent Communications, LLCTransitIPv4 IPv6295
AS204384LLC "OTT UKRAINE"HostingIPv4244
AS61335PE Denis PodolskiiUnclassifiedIPv4 IPv6152
AS206804Realcloud OUUnclassifiedIPv4132
AS29531VM Telecom, s.r.o.UnclassifiedIPv4107
AS60585SITEL-VSAT sroUnclassifiedIPv4 IPv6103
AS48473Towercom a.s.UnclassifiedIPv432
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv614

All 14 adjacent →

Provenance

Where this comes from

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