Policy Agile Solutions Provider operates under ASN 328748 and maintains a selective peering policy. We reserve the right to refuse or terminate peering with any party at our discretion. This policy applies equally to both IPv4 and IPv6 peering.
What Agile Solutions Provider Will Do 1. Announce only prefixes legitimately assigned to Agile or received from Agile customers. 2. Maintain up-to-date route objects in a route registry. 3. Maintain an up-to-date PeeringDB entry for AS328748. 4. Provide peers with a monitored, reachable email address for peering-related issues. 5. Support both public and private peering arrangements. 6. Encourage peering at multiple mutual locations, though not mandatory. 7. Ensure peering links remain uncongested and upgrade congested links promptly. 8. Apply anti-spoofing measures and follow BCP38 routing security practices. 9. Adhere to MANRS principles. 10. Promptly address any routing mistakes or prefix leaks. 11. Honor Multi-exit Discriminator (MED) bits. 12. Avoid unnecessary de-aggregation of prefixes.
What We Expect From Our Peers 1. Announce only prefixes legitimately assigned to them or their customers. 2. Avoid excessive prepending and unnecessary de-aggregation. 3. Apply BCP38 concepts and adhere to MANRS principles where feasible. 4. Provide monitored contact details for peering-related issues. 5. Maintain route objects in a route registry. 6. Ensure sufficient capacity on peering links to avoid congestion. 7. Maintain an up-to-date PeeringDB entry. 8. Be open to implementing RPKI signing if requested.
Peering Requirements - We do not require minimum traffic volumes, traffic ratios, or contracts for public peering. - We may consider contracts for private peering if requested. - We generally do not peer with route servers.
Peering Restrictions - We do not peer with our customers. - We may decline peering with networks that are customers of our customers. - Peering does not provide IP Transit, Internet Access, or access to on-net CDN/caching infrastructure.
Route Filtering Policy - We primarily rely on max-prefix limits for peer route control. - We do not perform prefix or AS_PATH filtering on peer routes. - We perform strict prefix, AS_PATH, and max-prefix filtering on all customer BGP sessions. - We do not accept: IPv4 prefixes longer than /24, IPv6 prefixes longer than /48, private/reserved IP space, or private ASNs. - We do not implement uRPF on peering routers.
Technical Requirements - Peering sessions must be direct eBGP (no Multi-Hop) using public ASNs and public address space only. - We exchange both IPv4 and IPv6 routes. - We announce routes consistently across all peering sessions, except for customer-specific traffic engineering. - Peers should not point default routes toward Agile Solutions Provider.
Peering Contact Information For peering inquiries: [email protected] Peering locations: For a list of exchange points and data centre facilities where you can peer with AgileSP, please visit our PeeringDB record.