Observed topology
AS47775 UBN-TRANSIT-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS47775: 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 |
|---|---|---|---|---|
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 33 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 32 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 22 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 5 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 3 |
| AS24482 | SG.GS | Hosting | IPv4 | 1 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 1 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS47775 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS24955 | JSC "Ufanet" | Residential | IPv4 IPv6 | 13,414 |
| AS41704 | JSC "Ufanet" | Unclassified | IPv4 | 1,680 |
| AS47119 | JSC "Ufanet" | Unclassified | IPv4 | 428 |
| AS60192 | JSC "Ufanet" | Unclassified | IPv4 | 300 |
| AS57128 | JSC "Ufanet" | Unclassified | IPv4 | 240 |
| AS60095 | JSC "Ufanet" | Unclassified | IPv4 IPv6 | 124 |
| AS39593 | JSC "Ufanet" | Unclassified | IPv4 | 60 |
Adjacency
Adjacent networks
Every AS seen directly next to AS47775 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS24955 | JSC "Ufanet" | Residential | IPv4 IPv6 | 13,630 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 5,465 |
| AS43298 | Storm Networks LLC | Unclassified | IPv4 | 4,944 |
| AS59796 | StormWall s.r.o. | Unclassified | IPv4 | 4,228 |
| AS41704 | JSC "Ufanet" | Unclassified | IPv4 | 1,680 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 1,146 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 648 |
| AS47119 | JSC "Ufanet" | Unclassified | IPv4 | 428 |
| AS60192 | JSC "Ufanet" | Unclassified | IPv4 | 300 |
| AS57128 | JSC "Ufanet" | Unclassified | IPv4 | 240 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.18M 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.