AS197658

A personal network with its router in Amsterdam

AS197658 is my own autonomous system. The core router, ams-core1, sits in Amsterdam and runs BIRD 2, configured through Pathvector. It announces a handful of IPv6 prefixes, peers over WireGuard tunnels and at IXP route servers, and gives transit to downstream networks.

I filter strictly. Routes have to match IRR objects, RPKI-invalid routes are dropped, and ASPA is checked where objects exist. Bogon and max-prefix filters run on every session. The network is a MANRS participant.

Right now

Announced prefixes

Neighbours, as RIPE RIS sees them

Data from RIPEstat and status.as197658.de, loading. Refresh

Peering

Peering is open. If you have valid ROAs and IRR route objects for what you announce, you'll get my routes from the route servers at the exchanges we share, and I'll set up a direct session over WireGuard if you'd like one. The rules are written down in the peering policy, and sessions are requested through the peering portal.

Downstreams need a valid ROA and a route object for every prefix, must never leak a default route, and have to deal with abuse reports within 24 hours.

I won't peer with networks that host DDoS or amplification sources, spam, malware, Tor exit nodes or illegal content, or with ASNs on the Spamhaus DROP list. The full list is in the policy.

Elsewhere

• bgp.tools: prefixes, upstreams and a graph, plus the BGP communities I support
• RIPEstat: routing history and visibility
• PeeringDB
• Looking glass: ping, traceroute and BGP lookups from my router
• Peering portal: request and manage sessions
• Status page

Contact

For anything network related, including abuse reports, write to noc@as197658.de.