Observed topology
AS49453 GLOBALLAYER
Hosting DROP-listed space RIPE Content
Transit
Upstream networks
Networks observed carrying traffic for AS49453: 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 |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,621 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 1,517 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,511 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 837 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 259 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 140 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 138 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 138 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 135 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 135 |
Transit
Downstream networks
Networks for which AS49453 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS136787 | PacketHub S.A. | VPN | IPv4 | 370 |
| AS51447 | RootLayer Web Services LLC | Unclassified | IPv4 | 244 |
| AS212810 | GODLIKE DIGITAL SOLUTIONS S.R.L. | Unclassified | IPv4 IPv6 | 217 |
| AS58181 | ULTRANEX LTD | Unclassified | IPv4 | 183 |
| AS203156 | Relayify LLC | Unclassified | IPv4 | 125 |
| AS57172 | Global Layer B.V. | Unclassified | IPv4 | 122 |
| AS211001 | TTR IT Holdings Limited | Unclassified | IPv4 IPv6 | 95 |
| AS47786 | Levrinets Olexander Andriyovich | Unclassified | IPv4 | 61 |
| AS267784 | Flyservers S.A. | Unclassified | IPv4 | 60 |
| AS198486 | Magna Pars Internet Technologies LTD | Unclassified | IPv4 | 8 |
Adjacency
Adjacent networks
Every AS seen directly next to AS49453 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,946 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,827 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 1,817 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 982 |
| AS136787 | PacketHub S.A. | VPN | IPv4 | 370 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 305 |
| AS51447 | RootLayer Web Services LLC | Unclassified | IPv4 | 244 |
| AS212810 | GODLIKE DIGITAL SOLUTIONS S.R.L. | Unclassified | IPv4 IPv6 | 217 |
| AS58181 | ULTRANEX LTD | Unclassified | IPv4 | 183 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 165 |
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.