asn.dev

Observed topology

AS49102 CONNECTED

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS49102: 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, LLCTransitIPv4 IPv6149
AS24482SG.GSHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS15718FROSTWEB LLCUnclassifiedIPv4118
AS41744KSK.NET s.c.UnclassifiedIPv459
AS51648GIGAINTERNET Sp z o.o.ResidentialIPv440
AS40961SERWIS S.C.ResidentialIPv434
AS207379Xtend New Media Sp. z o. o.UnclassifiedIPv415
AS198469Marek WajdzikUnclassifiedIPv413
AS48047Lukasz Chrustek Krakowskie Centrum Przetwarzania DanychUnclassifiedIPv412
AS62201Krzysztof Trzop trading as KTM TelekomResidentialIPv44
AS198928UT SP. Z O.O.UnclassifiedIPv41

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6450
AS15718FROSTWEB LLCUnclassifiedIPv4118
AS41744KSK.NET s.c.UnclassifiedIPv459
AS51648GIGAINTERNET Sp z o.o.ResidentialIPv451
AS40961SERWIS S.C.ResidentialIPv434
AS207379Xtend New Media Sp. z o. o.UnclassifiedIPv415
AS198469Marek WajdzikUnclassifiedIPv413
AS48047Lukasz Chrustek Krakowskie Centrum Przetwarzania DanychUnclassifiedIPv412
AS24482SG.GSHostingIPv46
AS62201Krzysztof Trzop trading as KTM TelekomResidentialIPv44

Provenance

Where this comes from

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