Observed topology
AS49592 PIPE-NET Pipe Networks GmbH
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS49592: 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 |
|---|---|---|---|---|
| AS49581 | Ferdinand Zink trading as Tube-Hosting | Hosting | IPv4 IPv6 | 548 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 IPv6 | 283 |
| AS34779 | T-2, d.o.o. | Residential | IPv4 IPv6 | 156 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 77 |
| AS62403 | PletX GmbH | Unclassified | IPv4 | 50 |
| AS212477 | RoyaleHosting BV | Hosting | IPv6 | 30 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 8 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 7 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 4 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS49592 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS203156 | Relayify LLC | Unclassified | IPv4 | 2,424 |
| AS210654 | Des Capital B.V. | Unclassified | IPv4 | 980 |
| AS199412 | ANARCHY LAB S.R.L. | Unclassified | IPv4 | 543 |
| AS207700 | Reliable Communications s.r.o. | Unclassified | IPv4 | 421 |
| AS219177 | RCS Technologies FZE LLC | Unclassified | IPv4 | 421 |
| AS199550 | HIRAGI LTD | Unclassified | IPv4 | 384 |
| AS219117 | TA Consulting & Services GmbH | Unclassified | IPv4 | 120 |
| AS395904 | Servury | Unclassified | IPv4 IPv6 | 98 |
| AS30042 | Boerboel LLC | Unclassified | IPv4 | 78 |
| AS203861 | Miteflux Technologies Ltd | Unclassified | IPv4 | 61 |
Adjacency
Adjacent networks
Every AS seen directly next to AS49592 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 IPv6 | 2,648 |
| AS203156 | Relayify LLC | Unclassified | IPv4 | 2,424 |
| AS62403 | PletX GmbH | Unclassified | IPv4 | 1,674 |
| AS49581 | Ferdinand Zink trading as Tube-Hosting | Hosting | IPv4 IPv6 | 1,587 |
| AS210654 | Des Capital B.V. | Unclassified | IPv4 | 980 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 669 |
| AS199412 | ANARCHY LAB S.R.L. | Unclassified | IPv4 | 543 |
| AS207700 | Reliable Communications s.r.o. | Unclassified | IPv4 | 421 |
| AS219177 | RCS Technologies FZE LLC | Unclassified | IPv4 | 421 |
| AS199550 | HIRAGI LTD | Unclassified | IPv4 | 384 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.