Observed topology
AS64010 BASICBRIX-AS-AP BasicBrix LLP
Hosting ARIN Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS64010: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 431 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 145 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 70 |
| AS38182 | Extreme Broadband - Total Broadband Experience | Residential | IPv4 | 63 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 9 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 8 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 8 |
| AS37989 | DCS1 Pte. Ltd. | Hosting | IPv4 IPv6 | 8 |
| AS61292 | Blix Group AS | Unclassified | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS64010 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS204957 | ROUTE 95 LLC | Unclassified | IPv4 IPv6 | 93 |
Adjacency
Adjacent networks
Every AS seen directly next to AS64010 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 474 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 164 |
| AS204957 | ROUTE 95 LLC | Unclassified | IPv4 IPv6 | 93 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 92 |
| AS38182 | Extreme Broadband - Total Broadband Experience | Residential | IPv4 | 63 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 11 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 10 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 10 |
| AS37989 | DCS1 Pte. Ltd. | Hosting | IPv4 IPv6 | 10 |
| AS61292 | Blix Group AS | Unclassified | IPv6 | 2 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.