Routing & Peering Policy
IPv6-first
RPKI required
IRR clean
Open peering
IX peering
AS215685 operates an open peering policy focused on stable IPv6 paths, consistent routing data and transparent policies.
Routing & Validation
- All prefixes have valid ROAs and are announced only when RPKI-valid.
- IRR data: maintained in set
AS215685:AS-T1. - Filtering: strict IRR/RPKI validation (reject: RPKI invalid, bogons, unallocated).
- PeeringDB: AS215685 – kept up to date.
Peering & Locations
Open peering for IRR/RPKI-validated networks. Bilateral sessions and IX fabrics:
- Frankfurt (DE) – DE-CIX
- Düsseldorf (building) – LocIX / remote
- Amsterdam (remote) – AMS-IX / Speed-IX
Remote peering accepted; multihop on request.
Contact & Peering Requests
Request peering via PeeringDB or through the contact form.
- Required: valid ROAs & current IRR/PeeringDB data
- Preferred: IPv6 peering
- Route servers optional; private sessions available
At a glance: IPv6-first · RPKI required · IRR clean · Open peering · IX/remote peering accepted
Prefixes
Current prefixes
| Prefix | Type | Status |
|---|
POP Status & Traffic
Total Traffic
Inbound (sum)—
Outbound (sum)—
loading…
Internet Exchanges
Active presence of AS215685
Loading PeeringDB…
Contact
We look forward to your message