asn.dev

Observed topology

AS51248 HOST-TELECOM Host-Telecom.com s.r.o.

Hosting RIPE

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS51248: 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
AS1299Arelion Sweden ABTransitIPv4317
AS9002RETN LimitedUnclassifiedIPv4 IPv6278
AS6939Hurricane Electric LLCTransitIPv4 IPv6211
AS174Cogent Communications, LLCTransitIPv4 IPv6179
AS3223Voxility LLPHostingIPv4166
AS3257GTT Communications Inc.TransitIPv4 IPv6104
AS29208Quantcom, a.s.UnclassifiedIPv436
AS24482SG.GSHostingIPv4 IPv625
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv625
AS34927iFog GmbHHostingIPv420

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS62212SmartApe OUUnclassifiedIPv4 IPv61,086
AS215305Mastersoft S.R.L.UnclassifiedIPv4471
AS199669Okay-Telecom Ltd.HostingIPv459
AS216024ALEKSEI FEDOROV PR KRUSEVACUnclassifiedIPv459

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS62212SmartApe OUUnclassifiedIPv4 IPv61,805
AS1299Arelion Sweden ABTransitIPv41,037
AS9002RETN LimitedUnclassifiedIPv4 IPv6894
AS6939Hurricane Electric LLCTransitIPv4 IPv6529
AS215305Mastersoft S.R.L.UnclassifiedIPv4471
AS174Cogent Communications, LLCTransitIPv4 IPv6423
AS3223Voxility LLPHostingIPv4296
AS3257GTT Communications Inc.TransitIPv4 IPv6279
AS29208Quantcom, a.s.UnclassifiedIPv481
AS24482SG.GSHostingIPv4 IPv665

Provenance

Where this comes from

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