Observed topology
AS49544 I3DNET
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS49544: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,102 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,084 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 964 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 767 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 363 |
| AS1403 | EBOX | Residential | IPv4 IPv6 | 262 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 231 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 226 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 194 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 179 |
Transit
Downstream networks
Networks for which AS49544 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS58272 | LeaderTelecom B.V. | Unclassified | IPv4 IPv6 | 8,275 |
| AS62370 | Snel.com B.V. | Unclassified | IPv4 IPv6 | 1,071 |
| AS141383 | VERGE CLOUD PRIVATE LIMITED | Hosting | IPv4 IPv6 | 875 |
| AS56851 | PE Skurykhin Mukola Volodumurovuch | Unclassified | IPv4 | 851 |
| AS53991 | Acronis | Unclassified | IPv4 IPv6 | 812 |
| AS200851 | Bamboozle Web Services MEA FZ-LLC | Hosting | IPv4 IPv6 | 313 |
| AS5419 | Cubic Circle B.V. | Unclassified | IPv4 | 303 |
| AS42473 | Anexia Cloud Solutions GmbH | Hosting | IPv4 IPv6 | 243 |
| AS13720 | Daybreak Game Company LLC | Hosting | IPv4 | 220 |
| AS211769 | Springer Nature B.V. | Unclassified | IPv4 IPv6 | 217 |
Adjacency
Adjacent networks
Every AS seen directly next to AS49544 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 9,073 |
| AS58272 | LeaderTelecom B.V. | Unclassified | IPv4 IPv6 | 8,275 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,631 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,614 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,302 |
| AS62370 | Snel.com B.V. | Unclassified | IPv4 IPv6 | 1,071 |
| AS141383 | VERGE CLOUD PRIVATE LIMITED | Hosting | IPv4 IPv6 | 875 |
| AS56851 | PE Skurykhin Mukola Volodumurovuch | Unclassified | IPv4 | 851 |
| AS53991 | Acronis | Unclassified | IPv4 IPv6 | 812 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 738 |
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.