> ## Documentation Index
> Fetch the complete documentation index at: https://docs.megaport.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Extreme IX Peering Request Procedures

> This help topic describes how to verify content provider availability and establish Route Server and Fast Peering Router sessions with Extreme IX.

Extreme IX operates carrier-neutral internet exchange points across major regional hubs in India. This topic consolidates the location-specific parameters, provider contact details, portal links, and peering instructions you need to set up peering.

## Verify content provider availability

Before you request peering, confirm that the content provider or peer network you want to reach is active at your Extreme IX location: Delhi, Mumbai, Chennai, Hyderabad, Kolkata, Bangalore, or Pune.

1. Go to the [Extreme IX content providers page](https://extreme-ix.org/members/content-providers).
2. Find your target provider's ASN and confirm availability under your location column.

## Establish Route Server and Fast Peering Router sessions

Establish BGP sessions with the Extreme IX Route Servers, and with the Fast Peering Router where available, to automatically receive routes from participating content networks.

### Regional infrastructure connection details

<AccordionGroup>
  <Accordion title="Delhi">
    | Component           | Remote IPv4      | Remote IPv6            | Remote AS |
    | ------------------- | ---------------- | ---------------------- | --------- |
    | Route Server 1      | `45.120.248.200` | `2001:df2:1900:1::200` | `49378`   |
    | Route Server 2      | `45.120.248.240` | `2001:df2:1900:1::240` | `49378`   |
    | Fast Peering Router | `45.120.248.95`  | `2001:df2:1900:1::95`  | `135814`  |
  </Accordion>

  <Accordion title="Mumbai">
    | Component           | Remote IPv4      | Remote IPv6            | Remote AS |
    | ------------------- | ---------------- | ---------------------- | --------- |
    | Route Server 1      | `103.77.108.200` | `2001:df2:1900:2::200` | `49378`   |
    | Route Server 2      | `103.77.108.240` | `2001:df2:1900:2::240` | `49378`   |
    | Fast Peering Router | `103.77.108.12`  | `2001:df2:1900:2::12`  | `135814`  |
  </Accordion>

  <Accordion title="Chennai">
    | Component           | Remote IPv4      | Remote IPv6            | Remote AS |
    | ------------------- | ---------------- | ---------------------- | --------- |
    | Route Server 1      | `45.120.251.200` | `2001:df2:1900:3::200` | `49378`   |
    | Route Server 2      | `45.120.251.240` | `2001:df2:1900:3::240` | `49378`   |
    | Fast Peering Router | `45.120.251.12`  | `2001:df2:1900:3::12`  | `135814`  |
  </Accordion>

  <Accordion title="Hyderabad">
    | Component           | Remote IPv4      | Remote IPv6            | Remote AS |
    | ------------------- | ---------------- | ---------------------- | --------- |
    | Route Server 1      | `103.77.110.200` | `2001:df2:1900:4::200` | `49378`   |
    | Route Server 2      | `103.77.110.240` | `2001:df2:1900:4::240` | `49378`   |
    | Fast Peering Router | `103.77.110.222` | `2001:df2:1900:4::222` | `135814`  |
  </Accordion>

  <Accordion title="Kolkata">
    | Component      | Remote IPv4      | Remote IPv6            | Remote AS |
    | -------------- | ---------------- | ---------------------- | --------- |
    | Route Server 1 | `45.120.249.200` | `2001:df2:1900:5::200` | `49378`   |
    | Route Server 2 | `45.120.249.240` | `2001:df2:1900:5::240` | `49378`   |

    Kolkata has no Fast Peering Router.
  </Accordion>

  <Accordion title="Bangalore">
    | Component           | Remote IPv4   | Remote IPv6            | Remote AS |
    | ------------------- | ------------- | ---------------------- | --------- |
    | Route Server 1      | `38.10.0.200` | `2001:df2:1900:7::200` | `49378`   |
    | Route Server 2      | `38.10.0.240` | `2001:df2:1900:7::240` | `49378`   |
    | Fast Peering Router | `38.10.0.13`  | `2001:df2:1900:7::13`  | `135814`  |
  </Accordion>

  <Accordion title="Pune">
    | Component           | Remote IPv4       | Remote IPv6            | Remote AS |
    | ------------------- | ----------------- | ---------------------- | --------- |
    | Route Server 1      | `123.253.159.200` | `2001:df2:1900:6::200` | `49378`   |
    | Route Server 2      | `123.253.159.240` | `2001:df2:1900:6::240` | `49378`   |
    | Fast Peering Router | `123.253.159.100` | `2001:df2:1900:6::100` | `135814`  |
  </Accordion>
</AccordionGroup>

<Warning>
  * **Outgoing BGP filters** -- Create BGP filters for outgoing routes to advertise only your public IP pools. Do not advertise full transit routes or routes received from upstream providers.
  * **Re-announcement restriction** -- Never re-announce Extreme IX Route Server or Fast Peering Router IP prefixes to transit providers or third-party peers.
</Warning>

<Note>
  * **Configuration SLA** -- BGP configuration on Extreme IX Route Servers takes 1 to 2 business days after you raise a peering request.
  * **Fast Peering Router purpose** -- An L3 solution that provides traffic from providers (notably Google) that reject bilateral BGP requests with new members globally and are not Route Server members.
  * **Pune** -- Access to major co-located CDNs (Google GGC, Facebook FNA, Apple) in Pune is available through the Premium CDN add-on service. Contact your Extreme CSM to open a support ticket. Amazon is available for free bilateral peering in Pune.

  For information about how to use BGP communities to control route propagation, see [BGP Communities and Configuration Guide](/ix/extreme-ix/bgp-communities).
</Note>

## Provider-specific peering instructions

Once you confirm availability on the [content providers page](https://extreme-ix.org/members/content-providers), see [Provider Peering Instructions](/ix/extreme-ix/provider-peering-instructions) for the onboarding requirements specific to your target content provider.