Sign in with PeeringDB
Peering policy · AS6424

Edgoo Networks peering policy

Edgoo Networks operates AS6424 as a global network service provider. This policy applies to all public and private interconnection with AS6424. Revised 1 September 2026.

Request peering
01General policy
Policy typeSelective. We evaluate each request on mutual benefit: traffic volume, geographic overlap, route diversity and operational quality. There is no minimum traffic level for public peering, but we expect a reasonable exchange of traffic in both directions.
Public peeringOpen to any network on a shared Internet Exchange that meets the requirements below. We prefer route servers: we peer with the route servers at every exchange we are connected to, so most networks already receive our routes there.
Bilateral sessionsOffered to networks exchanging 2 Gbps or more with us, or that need deterministic paths. Requested through this portal.
Private peering (PNI)Considered case by case from 5 Gbps of sustained traffic. Preferred minimum port speed is 10G or 100G or 400G. Available at any facility listed above. Each party pays for its own cross-connect unless otherwise agreed.
LocationsPeering at multiple locations is preferred; announcements must be consistent at every point of interconnection. Single-location peering is accepted for regional networks.
Ratio and contractNo traffic ratio requirement. No written agreement is required; a request accepted through the portal or by e-mail constitutes the peering arrangement. Either party may end peering with 90 days' notice.
02Requirements for peers
PeeringDBA complete and current PeeringDB record with accurate IXLAN addresses, as-set and NOC contact. The portal provisions directly from this record; stale entries are the most common cause of delay.
IRRAll announced prefixes registered in an IRR as-set listed in your PeeringDB record (RIPE, ARIN, APNIC, LACNIC, AFRINIC or RADB). We build prefix filters from IRR data and refresh them daily.
RPKIValid ROAs for the prefixes you originate. We drop RPKI-invalid announcements on all sessions and encourage peers to do the same with ours.
Network operationsA 24×7 NOC reachable by e-mail and phone, and a published abuse contact. We expect a response to operational issues within four hours.
Routing hygieneAnnounce only your own and your customers' routes. No default route, no transit routes, no bogons, no prefixes longer than /24 (IPv4) or /48 (IPv6). Do not point default or static routes at our interfaces.
03Technical details
ProtocolsIPv4 and IPv6 unicast on separate BGP sessions. No multicast. RFC 8950 (IPv4 over IPv6 next-hop) is not supported on peering sessions.
Our announcementsWe announce RIPE::AS-EDGOO, covering AS6424 and its customer cone: up to 7 500 IPv4 and 2 000 IPv6 prefixes. Recommended max-prefix limits: 10 000 (IPv4) and 3 000 (IPv6).
Your announcementsWe apply a max-prefix limit based on your PeeringDB values plus a safety margin. Sessions that exceed the limit are shut down and restarted automatically after 30 minutes.
Session securityMD5 authentication available on request. GTSM (TTL security) and BFD supported at most exchanges; state your preference when requesting.
BGP communitiesSupported on request. We honour the well-known communities NO_EXPORT and NO_ADVERTISE.
MTUStandard 1500-byte MTU on IX peering LANs. Jumbo frames on PNIs by agreement.
Legacy ASNAS47787 was migrated to AS6424. Remaining sessions are being moved; new peering is established with AS6424 only.
04Operations
MaintenanceWe notify peers of planned maintenance affecting sessions at least 5 business days in advance, to the NOC contact in PeeringDB. We ask peers to do the same.
Looking glassOur routing table is visible at lg.edgoo.net. Check how we see your prefixes before opening a ticket.
Reporting issuesSend session problems to the NOC with the exchange, both peering IPs and a UTC timestamp in the subject line. Abuse reports go to the abuse contact, not the peering team.
SuspensionWe may suspend a session without notice if it leaks routes, carries traffic not covered by this policy, or threatens the stability of our network. We contact your NOC before re-enabling it.
Policy changesThis policy may change without notice. The current version is always on this page.
05How to request peering
PortalSign in with your PeeringDB account. The portal shows the exchanges we share, the sessions that already exist and lets you request new IPv4 or IPv6 sessions per exchange. Confirmation by e-mail, usually within 5 business days.
Before you requestCheck that:
  • your PeeringDB record lists the correct IX addresses, as-set and NOC contact;
  • your IRR as-set covers every prefix you will announce;
  • ROAs exist for the prefixes you originate;
  • you have set a max-prefix limit for AS6424 (10 000 IPv4 / 3 000 IPv6).
Private interconnectionE-mail peering@edgoo.com with the facility, port speed and expected traffic.