Observed topology
AS58057 SECUREBIT Securebit Autonomous System
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS58057: 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 | 768 |
| AS20473 | The Constant Company, LLC | Hosting | IPv4 IPv6 | 342 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 274 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 157 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 IPv6 | 128 |
| AS35661 | VIRTUA SYSTEMS SAS | Unclassified | IPv4 IPv6 | 77 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 60 |
| AS51519 | Karabro AB | Unclassified | IPv4 IPv6 | 41 |
| AS61138 | Zappie Host LLC | Unclassified | IPv6 | 37 |
| AS21738 | Rozint | Residential | IPv6 | 36 |
Transit
Downstream networks
Networks for which AS58057 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,278 |
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv6 | 1,035 |
| AS16276 | OVH SAS | Hosting | IPv4 IPv6 | 694 |
| AS12735 | TurkNet Iletisim Hizmetleri A.S. | Unclassified | IPv4 IPv6 | 640 |
| AS3561 | CenturyLink Communications, LLC | Hosting | IPv4 | 496 |
| AS57050 | DreamServer S.R.L. | Unclassified | IPv4 IPv6 | 308 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 286 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 282 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 IPv6 | 249 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 182 |
Adjacency
Adjacent networks
Every AS seen directly next to AS58057 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 1,039,674 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 992,882 |
| AS44393 | Securebit AG | Unclassified | IPv4 IPv6 | 764,792 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 679,963 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 634,765 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 IPv6 | 30,571 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 4,373 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 3,771 |
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv6 | 3,574 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 2,868 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 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.