Observed topology
AS43278 CASTLES-AS Castles LLC
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS43278: 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 |
|---|---|---|---|---|
| AS59796 | StormWall s.r.o. | Unclassified | IPv4 | 321 |
| AS43298 | Storm Networks LLC | Unclassified | IPv4 | 206 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 141 |
| AS57494 | Adman LLC | Unclassified | IPv4 | 63 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 43 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 19 |
| AS24482 | SG.GS | Hosting | IPv4 | 18 |
| AS25091 | IP-Max SA | Unclassified | IPv4 | 7 |
| AS31500 | Global Network Management Inc | Unclassified | IPv6 | 6 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv6 | 5 |
Transit
Downstream networks
Networks for which AS43278 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS213780 | Individual Entrepreneur Suvorov Maxim Sergeevich | Hosting | IPv4 | 244 |
| AS42151 | LLC "P24-SERVICE" | Unclassified | IPv4 | 64 |
| AS12695 | LLC Digital Network | Hosting | IPv4 | 61 |
| AS206247 | Savchuk Matvej Aleksandrovich | Unclassified | IPv4 | 61 |
| AS213787 | Individual Entrepreneur Mchedlidze Georgiy Vitalievich | Hosting | IPv4 | 61 |
| AS214653 | Artem Izbaenkov | Unclassified | IPv4 | 61 |
| AS216334 | New Hosting Technologies LLC | Unclassified | IPv4 | 60 |
| AS48925 | VibeGAMES B.V. | Hosting | IPv4 | 33 |
Adjacency
Adjacent networks
Every AS seen directly next to AS43278 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS59796 | StormWall s.r.o. | Unclassified | IPv4 | 551 |
| AS213780 | Individual Entrepreneur Suvorov Maxim Sergeevich | Hosting | IPv4 | 244 |
| AS43298 | Storm Networks LLC | Unclassified | IPv4 | 231 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 216 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 207 |
| AS57494 | Adman LLC | Unclassified | IPv4 | 127 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 70 |
| AS42151 | LLC "P24-SERVICE" | Unclassified | IPv4 | 64 |
| AS12695 | LLC Digital Network | Hosting | IPv4 | 61 |
| AS206247 | Savchuk Matvej Aleksandrovich | Unclassified | IPv4 | 61 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.