AS205018
Irsyad Khoirul Anwar

Personal ASN

Peering Policy and Network Information

PeeringDBView on PeeringDB

Peering Policy

Summary

This document defines the peering policies for irsyad.eu (AS205018).

Background

AS205018 is a non-profit personal ASN operated as part of a hobbynet project, focusing on IPv6 only connectivity and network experimentation. This network is built for learning, testing, and exploring internet routing technologies, and welcomes collaboration with others who share a passion for networking and open peering. We are always open to peering, ideas, and collaborations with anyone interested, and we hope you are open to peering with us too. Because the internet grows stronger when we build it together, let's grow and exchange knowledge in the spirit of open networking.

Policy Statement

irsyad.eu adopts an open peering policy, all networks matching the technical requirements below are welcome to peer with us. We aim to establish reliable and mutually beneficial peering sessions whenever possible. All peering sessions with AS205018:AS-SET will advertise routes registered in the RIPE IRR database, ensuring transparency and consistency in routing.

Geofeeds(RFC 8805)

Peering Requirements (General)

To be eligible for peering, each candidate must:

  • Use a registered public autonomous system (AS) number;
  • Publish valid contact information viaPeeringDB; and
  • Maintain valid AS and prefix records with a public Internet Routing Registry (IRR).

A peer may only send toward us traffic intended for a destination network we advertise.
The use of static or default routes toward us is not permitted.
Peers must ensure that their policies in PeeringDB (e.g. maximum prefix count) are kept accurate.

Encouraged but not required:

Operations

AS205018 periodically evaluates its peering policy and may update it to reflect operational needs or best practices. Route filtering may be applied at our discretion to ensure only appropriate prefixes are advertised over established peering sessions.
By default, we filter bogon prefixes (RFC 1918, 5735, 6598) and any default routes to maintain routing integrity.

Contacts

Abuse

Report Abuse— Reports of abusive activity originating from AS205018 (spam, DDoS, copyright violations, etc.)

Peering

Peering Request— Requests for new peering sessions or changes to existing sessions.

NOC

Ask Questions— All other routing/network related issues.