asn.dev

Observed topology

AS49542 AS-ARTPLANET

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS49542: 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
AS29076Citytelecom LLCHostingIPv4 IPv6527
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6309
AS1299Arelion Sweden ABTransitIPv630
AS24482SG.GSHostingIPv4 IPv619
AS37721Virtual Technologies & SolutionsResidentialIPv413
AS25091IP-Max SAUnclassifiedIPv410
AS34927iFog GmbHHostingIPv410

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207713GLOBAL INTERNET SOLUTIONS LLCHostingIPv4 IPv6153

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS29076Citytelecom LLCHostingIPv4 IPv6608
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6372
AS207713GLOBAL INTERNET SOLUTIONS LLCHostingIPv4 IPv6153
AS1299Arelion Sweden ABTransitIPv634
AS24482SG.GSHostingIPv4 IPv622
AS37721Virtual Technologies & SolutionsResidentialIPv415
AS25091IP-Max SAUnclassifiedIPv410
AS34927iFog GmbHHostingIPv410

Provenance

Where this comes from

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