Last updated: 2026-09-08

Peering Policy

Technical requirements and acceptable-use rules for all BGP sessions with AS197658 · IXP route servers, WireGuard tunnels and private peering alike.

Request Peering ← Back to Overview PeeringDB
Technical Requirements
RPKI / ROAMandatory
✓Valid, signed ROA for every prefix a peer announces
✓RPKI Origin Validation enforced on all sessions
✗RPKI-Invalid prefixes are rejected automatically
✗RPKI-Unknown prefixes may be rejected depending on session type
IRR ObjectsMandatory
✓Correctly registered inetnum / inet6num objects for announced space
✓Matching route / route6 objects in a recognised IRR (RIPE, RADB, …)
✓Filters generated via bgpq4/IRRd against your AS-SET
✗Sessions without valid IRR route objects are not accepted
Routing Security Strict filters enforced
IRR RPKI ASPA ROA Validated BOGON Filter Max-Prefix
// Objects must resolve for the exact ASN and prefixes announced on the session. Stale, missing, or mismatched objects will delay or block session activation. ASPA objects are recommended where supported by your upstreams.
Prohibited Activities
Illegal ActivityZero Tolerance
✗Distribution of illegal content (incl. CSAM, illegal weapons or drug trade)
✗Phishing, malware distribution & botnet C2 infrastructure
✗Fraud, scams & trading of stolen data or credentials
✗Copyright-infringing piracy / warez hosting
Tor NetworkZero Tolerance
✗Tor exit nodes
✗Tor relay & bridge nodes
✗Any anonymisation proxy used to obscure the origin of abuse
Spam & DDoSZero Tolerance
✗Spam / unsolicited bulk email origination
✗DDoS & amplification attacks (open resolvers, NTP/memcached reflection)
✗Booter / stresser services
✗Unauthorised port/vulnerability scanning & route hijacking
Enforcement
How Violations Are Handled
✗Zero-tolerance violations — illegal activity, Tor nodes, spam or DDoS — result in immediate session teardown without prior notice.
✓Technical non-compliance — missing or invalid ROA/IRR objects — gets a 48h grace period to remediate before the session is suspended.
✓Abuse reports sent to our NOC are acknowledged and handled within 24h.
✗Repeated or unresolved violations result in permanent refusal of future peering requests for the offending ASN.
How to Peer
NOC Contact
noc@as197658.de
→
PeeringDB
Peering information & IXP presence
↗
Looking Glass
BGP diagnostics · traceroute · ping
↗
BGP.tools - AS197658
ASN info, prefixes, graph
↗