Routing Policy

Network Overview

• Network Operator: XROUTE
• Autonomous System Number (ASN): AS58401
• Contact: peering@xroute.id

Prefix Advertisement Policy

• We announce only IP prefixes that are legitimately allocated or assigned to our organization or our customers.
• All prefixes advertised to external peers are explicitly authorized and manually verified prior to activation.
• Any change to advertised prefixes requires prior approval and operational validation.

Customer Route Policy

• Customer route announcements are accepted only for prefixes explicitly authorized by the customer.
• Authorization is validated using:
• RIR allocation / assignment records (WHOIS)
• IRR route / route6 objects (where applicable)
• Contractual or written authorization
• Unauthorized, overly specific, or unexpected prefixes are rejected.

Prefix Filtering

• Ingress and egress prefix filtering is applied on all external BGP sessions.
• Prefix filters are maintained manually and updated whenever authorized changes occur.
• Max-prefix limits are enforced to prevent route leaks and accidental misconfiguration.

ASN Validation

• BGP sessions are restricted to expected neighbor ASNs.
• Routes with incorrect or unexpected origin ASNs are rejected.

Routing Security Controls

• Manual prefix and ASN authorization
• Max-prefix thresholds with alerting
• Continuous BGP monitoring and operational review
• Incident response procedures for routing anomalies

RPKI

• RPKI Route Origin Validation is monitored and evaluated.
• Deployment and enforcement are reviewed as part of ongoing routing security improvements.

Peering Policy

• Peering is considered on a case-by-case basis.
• All peers must agree to exchange only legitimate and authorized prefixes.
• Route leaks or policy violations may result in session suspension.

Updates & Review

• This routing policy is reviewed periodically and updated as operational requirements evolve.