Routing Policy
We maintain a consistent routing policy across all interconnection points, with prefixes announced via BGP from highly available edge routers. Prefixes are sourced from directly allocated blocks and customer assignments, with strict route filtering and IRR-based prefix validation applied.
IP Space & Filtering
- IPv4 and IPv6 prefixes originate from Elite-owned address blocks.
- All routes are registered in IRR, including RIPE and RADb.
- RPKI ROAs are published and validated with invalid routes rejected.
- Max-prefix limits are enforced per peer.
AS-SET and Registry Info
Our published AS-SET is AS-ELITE and AS-ELITE-V6. This includes customer cone members and is maintained via RIPE DB. Peer networks should reference this object for proper filtering.
- AS-SET:
AS-ELITE - RIPE DB: View AS-ELITE object
- AS-SET:
AS-ELITE-V6 - RIPE DB: View AS-ELITE-V6 object