Observed topology
AS8038 6CONNECT
Hosting ARIN Content
Transit
Upstream networks
Networks observed carrying traffic for AS8038: 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 |
|---|---|---|---|---|
| AS56635 | XENYA inzeniring, proizvodnja in trgovina, d.o.o. Ljubljana | Unclassified | IPv4 IPv6 | 384 |
| AS5603 | Telekom Slovenije, d.d. | Mobile | IPv4 IPv6 | 118 |
| AS203993 | S.J.M. Steffann | Unclassified | IPv4 IPv6 | 81 |
| AS20473 | The Constant Company, LLC | Hosting | IPv4 IPv6 | 79 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 7 |
| AS213241 | TECHIT.BE SRL | Residential | IPv6 | 5 |
| AS1103 | SURF B.V. | Unclassified | IPv4 IPv6 | 4 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 4 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 4 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 4 |
Transit
Downstream networks
Networks for which AS8038 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS215771 | John David Verolme trading as VeroCon | Unclassified | IPv6 | 5 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8038 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS56635 | XENYA inzeniring, proizvodnja in trgovina, d.o.o. Ljubljana | Unclassified | IPv4 IPv6 | 384 |
| AS5603 | Telekom Slovenije, d.d. | Mobile | IPv4 IPv6 | 118 |
| AS203993 | S.J.M. Steffann | Unclassified | IPv4 IPv6 | 81 |
| AS20473 | The Constant Company, LLC | Hosting | IPv4 IPv6 | 79 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 8 |
| AS213241 | TECHIT.BE SRL | Residential | IPv6 | 6 |
| AS1103 | SURF B.V. | Unclassified | IPv4 IPv6 | 5 |
| AS215771 | John David Verolme trading as VeroCon | Unclassified | IPv6 | 5 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 4 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 4 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-19 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.