Observed topology
AS212396 FYFEWEB FyfeWeb Core Network
Hosting APNIC NSP
Transit
Upstream networks
Networks observed carrying traffic for AS212396: 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 | 329 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 174 |
| AS3170 | VeloxServ Communications Ltd | Hosting | IPv4 IPv6 | 94 |
| AS35200 | TransitX Ltd | Unclassified | IPv4 | 47 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 36 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 24 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 22 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 15 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 15 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 15 |
Transit
Downstream networks
Networks for which AS212396 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS214480 | Innova Communications Limited | Unclassified | IPv4 IPv6 | 528 |
| AS206300 | YUNYOO LTD | Unclassified | IPv4 IPv6 | 291 |
| AS214098 | Horizon Hosting Limited | Hosting | IPv4 IPv6 | 136 |
| AS212868 | Glitch Servers Ltd | Unclassified | IPv4 IPv6 | 135 |
| AS213576 | Robert Weir | Unclassified | IPv4 IPv6 | 98 |
| AS214188 | VoltHosting Ltd | Unclassified | IPv4 IPv6 | 98 |
| AS200027 | RDA GROUP LIMITED | Unclassified | IPv4 IPv6 | 97 |
| AS219115 | TROPICAL HOSTING LTD | Unclassified | IPv4 IPv6 | 97 |
| AS219040 | Breezenodes Ltd | Unclassified | IPv4 IPv6 | 84 |
| AS218805 | Stacklayer Communications Limited | Unclassified | IPv4 IPv6 | 72 |
Adjacency
Adjacent networks
Every AS seen directly next to AS212396 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,419 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 850 |
| AS214480 | Innova Communications Limited | Unclassified | IPv4 IPv6 | 724 |
| AS212683 | Olilo UK & Ireland Ltd. | Residential | IPv6 | 452 |
| AS206300 | YUNYOO LTD | Unclassified | IPv4 IPv6 | 291 |
| AS3170 | VeloxServ Communications Ltd | Hosting | IPv4 IPv6 | 246 |
| AS35200 | TransitX Ltd | Unclassified | IPv4 | 240 |
| AS214098 | Horizon Hosting Limited | Hosting | IPv4 IPv6 | 136 |
| AS212868 | Glitch Servers Ltd | Unclassified | IPv4 IPv6 | 135 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 115 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.