Observed topology
AS49542 AS-ARTPLANET
Unclassified RIPE
Transit
Upstream networks
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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29076 | Citytelecom LLC | Hosting | IPv4 IPv6 | 527 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 309 |
| AS1299 | Arelion Sweden AB | Transit | IPv6 | 30 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 19 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 13 |
| AS25091 | IP-Max SA | Unclassified | IPv4 | 10 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 10 |
Transit
Downstream networks
Networks for which AS49542 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS207713 | GLOBAL INTERNET SOLUTIONS LLC | Hosting | IPv4 IPv6 | 153 |
Adjacency
Adjacent networks
Every AS seen directly next to AS49542 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29076 | Citytelecom LLC | Hosting | IPv4 IPv6 | 608 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 372 |
| AS207713 | GLOBAL INTERNET SOLUTIONS LLC | Hosting | IPv4 IPv6 | 153 |
| AS1299 | Arelion Sweden AB | Transit | IPv6 | 34 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 22 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 15 |
| AS25091 | IP-Max SA | Unclassified | IPv4 | 10 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 10 |
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.