Observed topology
AS40676 AS40676 - Psychz Networks
Hosting ARIN Content
Transit
Upstream networks
Networks observed carrying traffic for AS40676: 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 |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 13,819 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 11,942 |
| AS4637 | Telstra Global | Unclassified | IPv4 IPv6 | 1,978 |
| AS133296 | Web Werks India Pvt. Ltd. | Residential | IPv4 IPv6 | 1,441 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 915 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 875 |
| AS49063 | Data Storage Center JSC | Unclassified | IPv6 | 70 |
| AS215457 | DCS LLC | Unclassified | IPv4 | 60 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 49 |
| AS9957 | KINX | Hosting | IPv4 | 37 |
Transit
Downstream networks
Networks for which AS40676 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS397423 | Tier.Net Technologies LLC | Hosting | IPv4 IPv6 | 5,090 |
| AS7489 | HostUS | Hosting | IPv4 IPv6 | 1,976 |
| AS399629 | BL Networks | Unclassified | IPv4 | 1,927 |
| AS46805 | Angelnet Limited | Unclassified | IPv4 IPv6 | 1,449 |
| AS41564 | Orion Network Limited | Hosting | IPv4 | 1,357 |
| AS206996 | ZAP-Hosting GmbH | Unclassified | IPv4 IPv6 | 1,355 |
| AS215595 | SparkTech LTD | Unclassified | IPv4 | 1,288 |
| AS7361 | DataZone Networks LLC | Unclassified | IPv4 | 1,176 |
| AS62633 | HostRush | Unclassified | IPv4 IPv6 | 1,076 |
| AS397373 | H4Y Technologies LLC | Hosting | IPv4 IPv6 | 682 |
Adjacency
Adjacent networks
Every AS seen directly next to AS40676 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 27,426 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 24,082 |
| AS397423 | Tier.Net Technologies LLC | Hosting | IPv4 IPv6 | 7,184 |
| AS4637 | Telstra Global | Unclassified | IPv4 IPv6 | 1,979 |
| AS7489 | HostUS | Hosting | IPv4 IPv6 | 1,976 |
| AS399629 | BL Networks | Unclassified | IPv4 | 1,927 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,686 |
| AS46805 | Angelnet Limited | Unclassified | IPv4 IPv6 | 1,449 |
| AS133296 | Web Werks India Pvt. Ltd. | Residential | IPv4 IPv6 | 1,441 |
| AS41564 | Orion Network Limited | Hosting | IPv4 | 1,357 |
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.