Observed topology
AS212027 PebbleHost PebbleHost Ltd
Hosting RIPE Content
Transit
Upstream networks
Networks observed carrying traffic for AS212027: 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 | 244 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 204 |
| AS42689 | Glide Student & Residential Limited | Residential | IPv4 IPv6 | 199 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 176 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 176 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 133 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 128 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 44 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 23 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 23 |
Transit
Downstream networks
Networks for which AS212027 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS201002 | PebbleHost Ltd | Unclassified | IPv4 IPv6 | 2,788 |
| AS215108 | WebDevAE FZE | Unclassified | IPv6 | 177 |
| AS36743 | Ausra LLC | Unclassified | IPv4 IPv6 | 168 |
| AS57483 | Ian Chilton | Unclassified | IPv4 IPv6 | 159 |
| AS134666 | Hoshi Network | Unclassified | IPv6 | 106 |
| AS214566 | Centerfield Ltd | Hosting | IPv6 | 74 |
| AS200890 | Jianfeng Ren | Unclassified | IPv6 | 72 |
| AS209556 | Benli Zhong | Unclassified | IPv6 | 72 |
| AS209503 | Zentyx Limited | Hosting | IPv4 | 60 |
| AS210814 | VUNIFY LTD | Unclassified | IPv4 | 60 |
Adjacency
Adjacent networks
Every AS seen directly next to AS212027 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS201002 | PebbleHost Ltd | Unclassified | IPv4 IPv6 | 2,788 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,392 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 864 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 777 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 601 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 451 |
| AS42689 | Glide Student & Residential Limited | Residential | IPv4 IPv6 | 292 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 210 |
| AS215108 | WebDevAE FZE | Unclassified | IPv6 | 177 |
| AS36743 | Ausra LLC | Unclassified | IPv4 IPv6 | 168 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.