Routing & Peering Policy
How AS215685 handles BGP, validation and peering.
IPv6-first
RPKI required
IRR clean
Open peering
IX / Remote peering
AS215685 runs an open peering policy at selected internet exchanges and via private interconnects. All announcements are validated against RPKI and IRR data, with a preference for IPv6.
Routing & validation
- All prefixes have valid ROAs and are announced only as RPKI-valid.
- IRR data maintained in set
AS215685:AS-T1. - Strict filtering: reject RPKI invalids, bogons and unallocated space.
- PeeringDB entry AS215685 kept up to date.
Locations & IX
- Frankfurt – NL-IX, FOG-IX
- Düsseldorf – LocIX
- Amsterdam – Frys-IX, ERA-IX
Peering & contact
- Open for IRR/RPKI-clean peers, remote peering welcome.
- IP-Transit for IPv6 possible on FRA and AMS Side (at Moment only with GRE and Wireguard tunnel)
- NOC / Peering: peering@dotnic.de
- Abuse: abuse@dotnic.de
- Peering requests via PeeringDB or contact form below.
At a glance: IPv6-first · RPKI required · IRR clean · Open peering.
Prefixes
Currently announced prefixes by AS215685.
| Prefix | Type | Status |
|---|
Status & Traffic
POP state and aggregate traffic across the network.
Total Traffic
Inbound
—
Outbound
—
loading…
Internet Exchanges
Where AS215685 is currently present.
Loading PeeringDB…
Contact
Peering, NOC or general questions – send a message.