AS198733 Helikon
AS198733 is operated by Helikon and registered with RIPE NCC (TR) since 2026-04-17.
It announces 1 IPv4 and 1 IPv6 prefixes, 100% of them RPKI valid.
RIPE RIS sees 2 upstream and peer networks and 0 downstream networks next to it.
PeeringDB lists it as an Enterprise network at 1 facility. Its peering policy is selective.
| Name | Helikon |
|---|---|
| Registry (RIR) | RIPE NCC |
| Country | Turkey (TR) |
| Delegated on | 2026-04-17 |
| Network type | Enterprise, Regional |
| Peering policy | Selective |
| IRR as-set | RIPE::AS198733:AS-HELIKON |
| Prefixes (IPv4 / IPv6) | 1 / 1 |
| RPKI valid | 100% (2 / 2) |
| Upstreams and peers | 2 |
| Downstream networks | 0 |
| Website | helikon.io |
Routing health
- AS198733 announces 1 IPv4 and 1 IPv6 prefixes.
- All 2 announced prefixes are RPKI valid.
- 2 upstreams and peers, 0 downstream networks seen.
For every check with the fix (IRR route objects, the RPKI state of each route, reverse DNS and the registration), run the full network report.
Announced prefixes 2
- 185.104.1.0/24
- 2001:3640::/29
Upstreams and peers 2
The networks RIPE RIS sees next to AS198733 in BGP paths, the most visible first.
Peering
Peering policy: Selective. Suggested max-prefix limits: 1 IPv4, 1 IPv6. PeeringDB record
| Facility | City | Country |
|---|---|---|
| Equinix IL4 - Istanbul | Istanbul | TR |
More about AS198733
Sources: RIR delegation data and PeeringDB (updated daily); routing from RIPEstat (RIPE NCC RIS and RPKI), refreshed daily. Routing data from 2026-11-14 13:29 UTC. The country is where the AS number was registered, not necessarily where the network operates.