Observed topology
AS150142 WOLAST-AS-AP Wolast Technologies
Unclassified ARIN Enterprise
Transit
Upstream networks
Networks observed carrying traffic for AS150142: 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 |
|---|---|---|---|---|
| AS134732 | Dot Internet | Residential | IPv4 | 293 |
| AS58768 | Daffodil Online Ltd. | Residential | IPv4 | 287 |
| AS133112 | Spectra Technologies Limited | Unclassified | IPv4 | 251 |
| AS30058 | FDCservers.net | Unclassified | IPv4 | 59 |
| AS45905 | Stargate Communications Ltd. | Unclassified | IPv4 | 25 |
| AS23470 | ReliableSite.Net LLC | Hosting | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS150142 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS150142 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS134732 | Dot Internet | Residential | IPv4 IPv6 | 671 |
| AS133112 | Spectra Technologies Limited | Unclassified | IPv4 | 347 |
| AS58768 | Daffodil Online Ltd. | Residential | IPv4 | 287 |
| AS140068 | Code For Host Inc Ltd | Unclassified | IPv4 IPv6 | 270 |
| AS139870 | BlueNet Communication JV Ltd. | Unclassified | IPv4 | 116 |
| AS154047 | IT Nut Hosting | Unclassified | IPv4 | 116 |
| AS154434 | Hoststall.com | Unclassified | IPv4 | 108 |
| AS30058 | FDCservers.net | Unclassified | IPv4 | 59 |
| AS153898 | TNR SOFT | Unclassified | IPv4 | 53 |
| AS153523 | Ummah Host BD | Unclassified | IPv4 | 37 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12: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.