Observed topology
AS28773 AS-MASTER Global Technologies of Ukraine LLC
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS28773: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 192 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 13 |
| AS3255 | LLC EKSINTECH | Unclassified | IPv4 | 10 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 5 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 4 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 3 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 2 |
| AS24482 | SG.GS | Hosting | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS28773 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8779 | KhmelnitskInfocom LTD | Residential | IPv4 IPv6 | 233 |
| AS213389 | Podolskie opticheskie seti Ltd. | Residential | IPv4 | 114 |
| AS43301 | MAGICOM Ltd | Unclassified | IPv4 | 109 |
| AS56522 | FOP Naryshkin Igor Sergeevich | Residential | IPv4 | 86 |
| AS56423 | FOP Lisovskiy Dmitro Sergiyovich | Unclassified | IPv4 | 68 |
| AS29469 | Global Technologies of Ukraine LLC | Unclassified | IPv4 | 63 |
| AS212604 | WiNet LLc | Residential | IPv4 | 35 |
| AS35325 | "INCOMPLAST SERVICE" LLC | Unclassified | IPv4 | 8 |
Adjacency
Adjacent networks
Every AS seen directly next to AS28773 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 788 |
| AS8779 | KhmelnitskInfocom LTD | Residential | IPv4 IPv6 | 349 |
| AS213389 | Podolskie opticheskie seti Ltd. | Residential | IPv4 | 114 |
| AS43301 | MAGICOM Ltd | Unclassified | IPv4 | 109 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 103 |
| AS56522 | FOP Naryshkin Igor Sergeevich | Residential | IPv4 | 86 |
| AS56423 | FOP Lisovskiy Dmitro Sergiyovich | Unclassified | IPv4 | 68 |
| AS43668 | "AS43668" LLC | Residential | IPv4 | 66 |
| AS29469 | Global Technologies of Ukraine LLC | Unclassified | IPv4 | 63 |
| AS212604 | WiNet LLc | Residential | IPv4 | 35 |
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.