PeeringDB Record Requirement

To activate and maintain a route server session, participants must list CXC in their PeeringDB record with the ASN and peering IP addresses assigned by CXC. CXC synchronises with PeeringDB at least every 6 hours.

Notice and Grace Period

If a participant's record no longer matches: a first notice is sent to the technical contact, a second notice after 3 days, and if the mismatch persists for 7 days the route server session is shut down. The session is restored automatically at the next synchronisation once the record is corrected.

If you have any problem updating your PeeringDB record, please contact the CXC Team at peering@cloudxchange.id.

MANRS
APIX
PeeringDB
IXP Manager