Observed topology
AS215348 GONET-AS Gnet LLC
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS215348: 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 |
|---|---|---|---|---|
| AS20771 | Caucasus Online Ltd. | Unclassified | IPv4 | 300 |
Transit
Downstream networks
Networks for which AS215348 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS208603 | Real Estate of Georgia JSC | Unclassified | IPv4 | 236 |
| AS205173 | JSC "Georgian Railway" | Unclassified | IPv4 | 186 |
| AS57881 | JSC ENERGO-PRO Georgia | Unclassified | IPv4 | 88 |
| AS56966 | Foodservice LTD | Unclassified | IPv4 | 59 |
| AS201651 | Superbet 2014, Ltd | Unclassified | IPv4 | 58 |
| AS51841 | JSC MFI IntelExpress | Unclassified | IPv4 | 19 |
| AS202065 | Alliance Global Net Ltd | Unclassified | IPv4 | 12 |
| AS49016 | JSC Georgian State Electrosystem | Unclassified | IPv4 | 8 |
Adjacency
Adjacent networks
Every AS seen directly next to AS215348 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20771 | Caucasus Online Ltd. | Unclassified | IPv4 | 966 |
| AS208603 | Real Estate of Georgia JSC | Unclassified | IPv4 | 236 |
| AS205173 | JSC "Georgian Railway" | Unclassified | IPv4 | 186 |
| AS57881 | JSC ENERGO-PRO Georgia | Unclassified | IPv4 | 88 |
| AS56966 | Foodservice LTD | Unclassified | IPv4 | 59 |
| AS201651 | Superbet 2014, Ltd | Unclassified | IPv4 | 58 |
| AS51841 | JSC MFI IntelExpress | Unclassified | IPv4 | 19 |
| AS202065 | Alliance Global Net Ltd | Unclassified | IPv4 | 12 |
| AS49016 | JSC Georgian State Electrosystem | Unclassified | IPv4 | 8 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-06 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.