Sign in with PeeringDB
AS6424 · peering.edgoo.net

Peer with us.

Sign in with PeeringDB and the portal matches your IX presence against ours: sessions that exist, sessions that are available, and a one-step request for IPv4 or IPv6. Every request is reviewed by an Edgoo network engineer before anything is configured.

Continue with PeeringDB Read the peering policy

Authentication is PeeringDB OAuth; only users with admin rights on an ASN in PeeringDB can request peering for it. No PeeringDB account? E-mail peering@edgoo.com.

41 facilities · 17 exchanges · 6 continents
Status
OperationalRoute servers at every IX
Traffic
+10TbpsGlobal network traffic
Prefixes
7 500 · 2 000IPv4 · IPv6, RIPE::AS-EDGOO
Policy
SelectiveNo ratio, no contract
Public peering

Internet Exchanges

Every exchange where AS6424 has a port. We peer with the route servers at each one, so most networks already receive our routes. Bilateral sessions can be requested through the portal for networks exchanging 2 Gbps or more.

ExchangeCityPortFacilityPeering
Greece Athens 10 Gbps Digital Realty ATH1/2/3 - Athens RS IPv4 + IPv6
Germany Frankfurt 100 Gbps Equinix FR5 - Frankfurt, KleyerStrasse RS IPv4 + IPv6
Portugal Lisbon 100 Gbps Equinix LS1 - Lisbon RS IPv4 + IPv6
Spain Madrid 100 Gbps Digital Realty Madrid MAD1-2 RS IPv4 + IPv6
Spain Madrid 100 Gbps Digital Realty Madrid MAD1-2 RS IPv4 + IPv6
Singapore Singapore 10 Gbps Equinix SG3 - Singapore RS IPv4 + IPv6
Australia Sydney 10 Gbps Equinix SY5 - Sydney RS IPv4 + IPv6
Frys-IXEurope
 Netherlands Fryslân 200 Gbps NIKHEF Amsterdam RS IPv4 + IPv6
Portugal Lisbon 100 Gbps Equinix LS1 - Lisbon RS IPv4 + IPv6
Portugal Lisbon 100 Gbps Equinix LS1 - Lisbon RS IPv4 + IPv6
Brazil São Paulo/SP 100 Gbps Ascenty SPO03 - São Paulo RS IPv4 + IPv6
Spain Madrid 100 Gbps Digital Realty Madrid MAD1-2 RS IPv4 + IPv6
LINX LON1Europe
 United Kingdom London 100 Gbps Digital Realty London LHR19 RS IPv4 + IPv6
United Kingdom Scotland 10 Gbps DataVita DV1 Lanarkshire RS IPv4 + IPv6
MASS-IXNorth America
 United States Boston 10 Gbps CoreSite - Boston (BO1) RS IPv4 + IPv6
Czechia Prague, Bratislava, Vienna, Frankfurt 100 Gbps Equinix FR5 - Frankfurt, KleyerStrasse RS IPv4 + IPv6
SFMIXNorth America
 United States San Francisco 100 Gbps Digital Realty SFO (200 Paul) RS IPv4 + IPv6
Synced from PeeringDB · 27 Oct 2026 02:30 · IX addresses shown after sign-in
Private interconnection

Facilities

Data centres where AS6424 has equipment. Private network interconnects are considered from 5 Gbps of traffic, case by case, on 10G or 100G or 400G ports. Each site links to its PeeringDB record.

Europe24 sites

BelgiumBelgium1

GermanyGermany1

EstoniaEstonia1

SpainSpain5

FranceFrance3

United KingdomUnited Kingdom6

GreeceGreece1

NetherlandsNetherlands2

PortugalPortugal3

SloveniaSlovenia1

North America6 sites

United StatesUnited States6

South America6 sites

BrazilBrazil6

Africa1 site

South AfricaSouth Africa1

Asia3 sites

IndiaIndia1

SingaporeSingapore2

Oceania1 site

AustraliaAustralia1

How a request works

Three steps, one review

Discovery is automated, so you only request sessions that don't exist yet. Every request is reviewed against our policy before anything is configured.

01 · AUTHENTICATE

Sign in with PeeringDB

No separate account. Choose the ASN you administer and the portal reads its IXLAN entries from your public PeeringDB record.

02 · DISCOVER

See what already exists

The portal lists the exchanges we share and checks our routers for existing sessions, including ones configured but not yet established. Only sessions that do not exist are offered.

03 · REQUEST

Select sessions, we provision

Pick IPv4, IPv6 or both per exchange. An Edgoo engineer reviews the request against the policy, configures our side and confirms by e-mail, usually within 5 business days.

Peering policy · AS6424

Peering policy

Edgoo Networks operates AS6424 as a global network service provider. We welcome peering that improves performance for our customers and yours. This policy sets out what we offer, what we ask of peers, and how sessions are run day to day.

Full policy page
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.