Observed topology
AS14315 1GSERVERS
Hosting DROP-listed space ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS14315: 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.
Transit
Downstream networks
Networks for which AS14315 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS53755 | Input Output Flood LLC | Hosting | IPv4 | 1,119 |
| AS53767 | iCastCenter | Hosting | IPv4 | 254 |
| AS46829 | Lamhosting LLC | Unclassified | IPv4 IPv6 | 184 |
| AS214483 | FiberPower LLC | Unclassified | IPv4 | 174 |
| AS152179 | GLOBAL COMMUNICATION NETWORK LIMITED | Residential | IPv4 | 118 |
| AS401640 | BULKVM LLC | Unclassified | IPv4 IPv6 | 92 |
| AS25894 | MX2 Technology, Inc | Unclassified | IPv4 | 60 |
| AS214390 | Wojtek SASU, trading as Gofile | Hosting | IPv6 | 33 |
| AS203391 | Cloud DNS Ltd | Hosting | IPv4 | 6 |
Adjacency
Adjacent networks
Every AS seen directly next to AS14315 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 3,157 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 1,594 |
| AS53755 | Input Output Flood LLC | Hosting | IPv4 | 1,129 |
| AS53767 | iCastCenter | Hosting | IPv4 | 940 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 720 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 477 |
| AS46829 | Lamhosting LLC | Unclassified | IPv4 IPv6 | 184 |
| AS214483 | FiberPower LLC | Unclassified | IPv4 | 174 |
| AS152179 | GLOBAL COMMUNICATION NETWORK LIMITED | Residential | IPv4 | 118 |
| AS401640 | BULKVM LLC | Unclassified | IPv4 IPv6 | 92 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-15 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.09M 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.