Extreme IX Provider Peering Instructions

Akamai (PNI and AANP)

Akamai PNI — Provided free from Akamai’s public nodes. You receive Akamai PNI prefixes through the Extreme Route Servers. There is no bilateral BGP for Akamai PNI traffic.
Akamai AANP — Paid traffic, provided from nodes installed in Extreme’s network. You receive Akamai AANP prefixes through the Extreme Route Servers. Contact your Account Manager to start this traffic, since it is part of the Premium CDN service. There is no bilateral BGP for Akamai AANP traffic.
DNS requirement — Akamai AANP peering depends on DNS. Do not use public DNS (such as 8.8.8.8 or L3 DNS servers). Use your own DNS server and advertise its IP address through your BGP sessions with the Extreme Route Servers.

Akamai Prolexic

Prolexic, part of Akamai, is a DDoS mitigation service. Peering gives you a short path to offload outbound DDoS traffic and improves proximity to mutual Akamai customers.

Interconnection details:
- Mumbai — IPv4 103.77.109.140, IPv6 2001:df2:1900:2::1140
- Chennai — IPv4 45.120.251.95, IPv6 2001:df2:1900:3::95
- ASN 32787, AS macro AS-PROLE
- Suggested max prefixes: 8000 (IPv4) / 800 (IPv6)
Support and peering contacts:
- Session modification/administrative — peering-tix@akamai.com, +1 617 444-3007
- 24/7 break/fix NOC — nocc-tix@akamai.com, +1 617 444-3007
SLA and policy — BGP configuration takes up to 10 business days. Akamai Prolexic applies a selective peering policy and can refuse bilateral BGP peering with some members.
Route Server note — Akamai Prolexic (AS32787) is also a Route Server member, so you also learn its routes through your Route Server sessions.

Amazon

Setup method — Register a request using the Amazon peering portal.
For detailed instructions, see Amazon Bilateral Peering.

Apple

Route Server note — Apple is not a Route Server member. You cannot learn Apple’s routes through the Extreme IX Route Servers.
Mandatory requirements — Apple only establishes bilateral sessions with members that maintain a fully populated PeeringDB record, including NOC contacts.
Estimated SLA — Up to 2 weeks after you raise the peering request.
Email request format:
- To: peering@group.apple.com
- Subject: Direct Apple Peering over Extreme IX [City Name] for <your Company name>
- Body:

Dear Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your NOC contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.

CacheFly

Setup method — Send email to peering@cachefly.com (NOC contact: noc@cachefly.com).
Policy and requirements — CacheFly does not peer with everyone. If you use the Route Servers, CacheFly prefers that you do not also request a bilateral session, since it advertises the same prefixes both ways.
SLA — Less than 2 days for bilateral session establishment.
Traffic type — CDN content, primarily not DNS-sensitive.

Cisco Umbrella

Estimated SLA — Up to 1 week after you raise the peering request.
Email request format:
- To: peering@opendns.com
- Subject: Direct Cisco Umbrella Peering over Extreme IX [City Name] for <your Company name>
- Body:

Dear Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your NOC contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.

CIRA DNS

Estimated SLA — 1 to 2 business days after you raise the peering request.
Email request format:
- To: peering@cira.ca
- Subject: Direct CIRA Bilateral Peering over Extreme IX [City Name] for <your Company name>
- Body:

Dear CIRA team,
We would like to Peer with you over Extreme - IX in [City Name]
Kindly find the details below:
ASN: -> [your AS Number]
Network name: -> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: -> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: -> [your noc contact details]
Kindly please tell us further steps.

Cloudflare

Estimated SLA — 2 to 3 weeks after you raise the peering request.
Public peering is automated through the Cloudflare Peering Portal. We recommend establishing sessions in all mutual locations. Use PeeringDB OIDC to authenticate.

DigitalOcean

Automation note — DigitalOcean’s automation tool pulls your contact details, v4 address, prefix count, and NOC contact directly from PeeringDB. Keep your PeeringDB information up to date.
Estimated SLA — 4 to 5 days after you raise the peering request.
Email request format:
- To: peering@digitalocean.com
- Subject: Direct DigitalOcean Bilateral Peering over Extreme IX [City Name] for <your Company name>
- Body:

Dear DigitalOcean team,
We would like to Peer with you over Extreme - IX in [City Name]
Kindly find the details below:
ASN: -> [your AS Number]
Network name: -> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: -> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: -> [your noc contact details]
Kindly please tell us further steps.

Facebook / Meta

Traffic threshold — Selective peering policy; your traffic to Facebook peering should exceed 50 Mbps.
Estimated SLA — 2 to 5 weeks after you raise the peering request.
Alternative request method — You can also use the Meta Peering Manager Portal to request bilateral peering.
Email request format:
- To: peering@fb.com
- Subject: Direct Facebook Bilateral Peering over Extreme IX [City Name] for <your Company name>
- Body:

Dear Facebook Peering team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your noc contact details]
Kindly please tell us further steps.

Fastly

Prerequisite — Create an IRR record; Fastly uses IRRs for route filtering.
Traffic threshold — Selective peering policy; your traffic to Fastly peering should exceed 50 Mbps.
Estimated SLA — 1 to 2 weeks after you raise the peering request.
Email request format:
- To: peering@fastly.com
- Subject: Direct Fastly Bilateral Peering over Extreme IX [City Name] for <your Company name>
- Body:

Dear Fastly Peering team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your noc contact details]
Kindly please tell us further steps.

Gcore

Estimated SLA — 2 to 3 weeks after you raise the peering request.
Email request format:
- To: noc@gcore.lu
- Subject: Direct Gcore Peering over Extreme IX [City Name] for <your Company name>
- Body:

Dear Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your noc contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.

IBM Cloud (AS36351)

Estimated SLA — 1 to 5 weeks after you raise the peering request.
Email request format:
- To: peering@softlayer.com
- Subject: Direct IBM Cloud Peering Request within Extreme IX [City Name] | <your Company name> <ASN>
- Body:

Dear IBM Cloud Peering team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [Your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [This is your Extreme IX IP]
v4 prefix count: --> [All of your prefix counts]
v6 address: - [This is your Extreme IX IPv6]
v6 prefix count: --> [All of your prefix counts]
NOC contact: --> [Your noc contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.

Joy Services (AS152565)

Joy Services is a Route Server member and also establishes bilateral sessions. For public services, it has DNS/name server routes available through the Route Servers. For end-user content — hosted files, API, DNS queries, CDN, cache servers, and database CDN cache — you must establish a bilateral session.

Estimated SLA — 20 minutes if you use the strict email format below, since it is processed by an automated API. Manual reviews take up to 24 hours.
Provider details:
- Official site — joy.services
- BGP tools — AS152565
- Technical contact — dinesh@joycloud.services
- Public resolver DNS — dns.joy.services
Email request format:
- To: support@joycloud.services
- Subject: Enabling Bilateral BGP Session - Extreme [City Name] || Joy Services - <company-name>
- Body:

Dear Peering team,
We would like to Peer with you over Extreme - IX [City Name]
ASN-[company_asn]
Network_name-[network_name]
Contact_email-[contact_team]
v4_address-[peering_address]
v4_prefix count-[total_prefix_count]
NOC-[noc_team_email]
Peering_db_link-[peering_db_link]
Other_Info-[any_general_info_saved_in_notes_by_our_system]

In Other_Info, specify 1 for India region only, or 2 for full routes for all content over Joy Services.

Kaopu Cloud HK

Route Server and bilateral note — Kaopu Cloud HK is a Route Server member and accepts bilateral BGP requests.
Estimated SLA — 3 to 5 working days after you raise the peering request.
Contact format — Send email to noc@kaopucloud.com, with a copy to apac@kaopucloud.com, providing your BGP configuration details (ASN, number of prefixes, and MD5 key if configured).

Melbicom

Estimated SLA — 1 to 3 days after you raise the peering request.
Email request format:
- To: peering@melbicom.net
- Subject: Direct Melbicom Bilateral Peering over Extreme IX [City Name] for <your Company name>
- Body:

Dear Melbicom Peering team,
We would like to Peer with you over Extreme - IX in [City Name]
Kindly find the details below:
ASN: -> [your AS Number]
Network name: -> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: -> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: -> [your noc contact details]
Kindly please tell us further steps.

Microsoft (Azure)

Setup method — Register a request using the Azure portal.
For step-by-step instructions, see Azure Bilateral Peering.

Netskope

Route Server and bilateral note — Netskope is a Route Server member and also accepts bilateral BGP requests.
Estimated SLA — 10 days after you raise the peering request.
Contact format — Send email to peering@netskope.com with your complete BGP configuration details, including ASN, number of prefixes, and MD5 key if configured.

Netflix

Setup method — Submit a request through the Netflix Open Connect Partner Help Center.
Estimated SLA — 2 to 4 weeks after you raise the peering request.

Oracle Cloud Infrastructure

Estimated SLA — 2 weeks after you raise the peering request.
Email request format:
- To: peering_ww@oracle.com
- Subject: Direct Oracle Cloud Infrastructure Peering over Extreme IX [City Name] for <your Company name>
- Body:

Dear Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your NOC contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.

OVH

Email request format:
- To: peering-16276@ovh.net
- Subject: Direct OVH Peering over Extreme IX [City Name] for <your Company name>
- Body:

Dear Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your noc contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.

Psychz Network

Estimated SLA — 2 to 3 weeks after you raise the peering request.
Email request format:
- To: support@psychz.net
- Subject: Direct Psychz Network Peering over Extreme IX [City Name] for <your Company name>
- Body:

Dear Psychz Network team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your noc contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.

Riot Games

Estimated SLA — 1 week after you raise the peering request.
Email request format:
- To: peering@riotgames.com
- Subject: Direct Riot Games Peering over Extreme IX [City Name] for <your Company name>
- Body:

Dear Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your NOC contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.

Times Internet

Route Server and bilateral note — Times Internet is a Route Server member and also establishes bilateral sessions.
Request directive — Times Internet does not provide a bilateral peering email address. It reaches out to peers directly.

Verge Cloud

Route Server note — You receive Verge Cloud prefixes exclusively through the Extreme IX Route Servers. Bilateral BGP sessions are not supported.
Public looking glass — Not available.
Traffic and queries — Content includes non-DNS-sensitive OTT, entertainment, trading, and CDN traffic. For peering-related queries, email peering@vergecloud.com.

Yahoo

Estimated SLA — 2 to 3 weeks after you raise the peering request.
Email request format:
- To: peering-requests@yahooinc.com (or peering-requests@oath.com for Chennai)
- Subject: Direct Yahoo Peering over Extreme IX [City Name] for <your Company name>
- Body:

Dear Yahoo Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your noc contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.

Zenlayer / Valve

Estimated SLA — Up to 2 weeks after you raise the peering request.
Email request format:
- To: peering@zenlayer.com (or peering@valvesoftware.com for Valve traffic in Chennai)
- Subject: Direct Zenlayer Bilateral Peering over Extreme IX [City Name] for <your Company name>
- Body:

Dear Zenlayer Peering team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your noc contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.

ZScaler Softech

Estimated SLA — Up to 1 week after you raise the peering request.
Email request format:
- To: peering@zscaler.com
- Subject: Direct ZScaler Softech Peering over Extreme IX [City Name] for <your Company name>
- Body:

Dear Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your NOC contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.

Route Server-only providers

The following providers exchange traffic exclusively through the Extreme IX Route Servers and do not accept or support bilateral BGP sessions:

BitGravity
Endurance International Group
F5 Inc.
Global Network Management (Telegram)
Infobip Peering
Leapswitch Networks
Rediff Peering

Connecting to the Extreme IX Route Servers automatically brings you prefixes from these members. No separate outreach is required.