Observed topology
AS214128 Empire-il-AS Ofek U. Havia
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS214128: 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 |
|---|---|---|---|---|
| AS199524 | G-Core Labs S.A. | Hosting | IPv4 | 111 |
| AS12400 | Partner Communications Ltd. | Unclassified | IPv4 IPv6 | 38 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 24 |
| AS24482 | SG.GS | Hosting | IPv6 | 2 |
| AS25091 | IP-Max SA | Unclassified | IPv6 | 2 |
| AS401753 | BIXCE Inc | Unclassified | IPv6 | 2 |
| AS49915 | Megaport (UK) Limited | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS214128 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS218447 | Itay Kariel | Unclassified | IPv4 IPv6 | 34 |
Adjacency
Adjacent networks
Every AS seen directly next to AS214128 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS199524 | G-Core Labs S.A. | Hosting | IPv4 | 111 |
| AS12400 | Partner Communications Ltd. | Unclassified | IPv4 IPv6 | 39 |
| AS49915 | Megaport (UK) Limited | Unclassified | IPv4 IPv6 | 34 |
| AS218447 | Itay Kariel | Unclassified | IPv4 IPv6 | 34 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 24 |
| AS24482 | SG.GS | Hosting | IPv6 | 2 |
| AS25091 | IP-Max SA | Unclassified | IPv6 | 2 |
| AS401753 | BIXCE Inc | Unclassified | IPv6 | 2 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-07 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.97M 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.