Observed topology
AS44854 ERITAP-AS Arend Brouwer
Hosting RIPE Network Services
Transit
Upstream networks
Networks observed carrying traffic for AS44854: 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 | 124 |
| AS25091 | IP-Max SA | Unclassified | IPv4 IPv6 | 71 |
| AS6206 | Netrouting B.V. | Hosting | IPv4 IPv6 | 47 |
| AS6424 | EDGOO NETWORKS UNIPESSOAL LDA | Hosting | IPv4 IPv6 | 26 |
| AS49127 | Asimo Networks B.V. | Hosting | IPv4 IPv6 | 19 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 7 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 7 |
| AS58057 | Securebit AG | Unclassified | IPv4 IPv6 | 7 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 6 |
| AS1836 | green.ch AG | Residential | IPv4 | 3 |
Transit
Downstream networks
Networks for which AS44854 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS211251 | A1 Internet BV | Unclassified | IPv4 | 136 |
| AS215877 | Erwin Alexander Ising | Unclassified | IPv6 | 62 |
| AS202419 | Inflexum Services B.V. | Unclassified | IPv4 IPv6 | 52 |
| AS206924 | Ben Cartwright-Cox | Unclassified | IPv6 | 37 |
| AS215473 | Elimalko Saado | Unclassified | IPv6 | 31 |
| AS218916 | Fiscale Inlichtingen en Opsporingsdienst (FIOD) | Unclassified | IPv4 IPv6 | 30 |
| AS202019 | Eric Kelderman trading as Bodega ICT | Unclassified | IPv4 | 24 |
| AS5418 | nerdnet | Unclassified | IPv4 | 21 |
| AS215665 | Marlon Alkan | Unclassified | IPv6 | 15 |
| AS205920 | iFog GmbH | Unclassified | IPv6 | 3 |
Adjacency
Adjacent networks
Every AS seen directly next to AS44854 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS25091 | IP-Max SA | Unclassified | IPv4 IPv6 | 307 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 208 |
| AS211251 | A1 Internet BV | Unclassified | IPv4 | 148 |
| AS215877 | Erwin Alexander Ising | Unclassified | IPv6 | 62 |
| AS6206 | Netrouting B.V. | Hosting | IPv4 IPv6 | 57 |
| AS202419 | Inflexum Services B.V. | Unclassified | IPv4 IPv6 | 52 |
| AS6424 | EDGOO NETWORKS UNIPESSOAL LDA | Hosting | IPv4 IPv6 | 49 |
| AS206924 | Ben Cartwright-Cox | Unclassified | IPv6 | 37 |
| AS215473 | Elimalko Saado | Unclassified | IPv6 | 31 |
| AS218916 | Fiscale Inlichtingen en Opsporingsdienst (FIOD) | Unclassified | IPv4 IPv6 | 30 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.