Observed topology
AS49824 ACTPA-AS Astra LLC
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS49824: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 673 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 481 |
| AS6663 | Euroweb Romania S.R.L. | Unclassified | IPv4 IPv6 | 415 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 396 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 43 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 39 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 IPv6 | 33 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 26 |
| AS56655 | Gigahost AS | Unclassified | IPv6 | 13 |
| AS201054 | Stowarzyszenie e-Poludnie | Unclassified | IPv6 | 13 |
Transit
Downstream networks
Networks for which AS49824 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS198820 | Limited Liability Company Radio Network | Unclassified | IPv4 | 688 |
| AS207475 | FOP Onuschak Oleg Volodimirovich | Unclassified | IPv4 IPv6 | 221 |
| AS207830 | LIMNET , LLC | Unclassified | IPv4 | 178 |
| AS197327 | TZOV FAVORIT | Unclassified | IPv4 | 65 |
| AS196906 | PE Brunarsky Andrey Romanovich | Residential | IPv4 | 64 |
| AS20516 | Sky Vision Ukraine Ltd | Residential | IPv4 | 62 |
| AS213979 | TzOV Space Net | Unclassified | IPv4 | 62 |
| AS200814 | LIMNET , LLC | Unclassified | IPv4 | 53 |
| AS48957 | Joint Ukrainian American Enterprise "Telecommunications Resource Center" ltd | Unclassified | IPv4 | 20 |
| AS49984 | "Telecomunikatsiina Companiya" Ltd | Residential | IPv4 | 15 |
Adjacency
Adjacent networks
Every AS seen directly next to AS49824 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,327 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 956 |
| AS198820 | Limited Liability Company Radio Network | Unclassified | IPv4 | 688 |
| AS6663 | Euroweb Romania S.R.L. | Unclassified | IPv4 IPv6 | 639 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 493 |
| AS207475 | FOP Onuschak Oleg Volodimirovich | Unclassified | IPv4 IPv6 | 221 |
| AS207830 | LIMNET , LLC | Unclassified | IPv4 | 178 |
| AS196906 | PE Brunarsky Andrey Romanovich | Residential | IPv4 | 128 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 67 |
| AS197327 | TZOV FAVORIT | Unclassified | IPv4 | 65 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-22 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.12M 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.