Observed topology
AS3300 BT
Residential DROP-listed space RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS3300: 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 | 1,597 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,533 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,244 |
| AS4637 | Telstra Global | Unclassified | IPv4 IPv6 | 863 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 606 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 606 |
| AS4657 | StarHub Ltd | Residential | IPv4 IPv6 | 315 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 244 |
| AS1403 | EBOX | Residential | IPv4 IPv6 | 198 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 183 |
Transit
Downstream networks
Networks for which AS3300 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS7246 | Bristol-Myers Squibb Company | Unclassified | IPv4 IPv6 | 569 |
| AS72 | Schlumberger Limited | Unclassified | IPv4 | 290 |
| AS136767 | BMW AG (Bayerische Motoren Werke Aktiengesellschaft) | Unclassified | IPv4 IPv6 | 279 |
| AS22683 | Koninklijke Philips N.V. | Unclassified | IPv4 | 232 |
| AS18872 | Veritas Technologies LLC | Unclassified | IPv4 IPv6 | 203 |
| AS40659 | BMW of North America, LLC (Group Data Centers America) | Unclassified | IPv4 IPv6 | 182 |
| AS78 | BT Americas, Inc | Unclassified | IPv4 | 174 |
| AS399449 | Kyndryl | Unclassified | IPv4 | 174 |
| AS141399 | Specsavers Pty Ltd | Unclassified | IPv4 | 116 |
| AS212565 | Specsavers Optical Group Limited | Unclassified | IPv4 | 116 |
Adjacency
Adjacent networks
Every AS seen directly next to AS3300 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,143 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 2,058 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,619 |
| AS4637 | Telstra Global | Unclassified | IPv4 IPv6 | 1,197 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 790 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 761 |
| AS4657 | StarHub Ltd | Residential | IPv4 IPv6 | 698 |
| AS7246 | Bristol-Myers Squibb Company | Unclassified | IPv4 IPv6 | 569 |
| AS72 | Schlumberger Limited | Unclassified | IPv4 | 290 |
| AS136767 | BMW AG (Bayerische Motoren Werke Aktiengesellschaft) | Unclassified | IPv4 IPv6 | 279 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.