ixreport

SP-iXP Route Servers

AS137179 · SmartCyber

SCN Telecom Private Limited

1Exchange
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Route ServerType
OpenPeering policy
1Using the route servers
1To fix in PeeringDB
4Facilities in PeeringDB

Tools: Where can I peer with SP-iXP Route Servers? · Where should SP-iXP Route Servers peer next? · Compare SP-iXP Route Servers with another network

This network elsewhere: the registry history of AS137082-AS137181, the block AS137179 is in, on RIR Tracker

PeeringDB fix list Printable page · CSV

One thing to fix in SP-iXP Route Servers's PeeringDB record, from what its exchanges publish: 1 at exchanges that look shut down. As of 2026-11-19 18:41 UTC.

Make the changes on SP-iXP Route Servers's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Exchanges that look shut down (1)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. Only one outside network

    IPv4103.147.193.2
    IPv6–
    Speed40000 Mbps (40G)
    IPv4103.147.193.3
    IPv6–
    Speed40000 Mbps (40G)

Exchanges over time

01Oct 3, 2026Nov 19, 20261
Show as a table
DateExchanges
Nov 19, 20261
Nov 18, 20261
Nov 17, 20261
Nov 16, 20261
Nov 15, 20261
Nov 14, 20261
Nov 13, 20261
Nov 12, 20261
Nov 11, 20261
Nov 10, 20261
Nov 9, 20261
Nov 8, 20261
Nov 7, 20261
Nov 6, 20261
Nov 5, 20261
Nov 4, 20261
Nov 3, 20261
Nov 2, 20261
Nov 1, 20261
Oct 31, 20261
Oct 30, 20261
Oct 29, 20261
Oct 28, 20261
Oct 27, 20261
Oct 26, 20261
Oct 25, 20261
Oct 24, 20261
Oct 23, 20261
Oct 22, 20261
Oct 21, 20261
Oct 20, 20261
Oct 19, 20261
Oct 18, 20261
Oct 17, 20261
Oct 16, 20261
Oct 15, 20261
Oct 14, 20261
Oct 13, 20261
Oct 12, 20261
Oct 11, 20261
Oct 10, 20261
Oct 9, 20261
Oct 8, 20261
Oct 7, 20261
Oct 6, 20261
Oct 5, 20261
Oct 4, 20261
Oct 3, 20261

Map

Where SP-iXP Route Servers's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 80G across 1 exchange.

India SP-iXP Mumbaighost Mumbai, India 103.147.193.2
103.147.193.3
2 × 40G Yes PeeringDB

Exchanges in its buildings that it isn't on (10)

These exchanges have a switch in a facility where SP-iXP Route Servers lists itself in PeeringDB, but don't have SP-iXP Route Servers as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

India DE-CIX MumbaiMumbai, India 454 Sify Rabale - Mumbai
India Extreme IX MumbaiMumbai, India 246 CtrlS Mumbai DC1; Sify Rabale - Mumbai
India Extreme IX DelhiDelhi, India 173 CtrlS Noida DC1
India NIXI DelhiDelhi, India 114 CtrlS Noida DC1
India DE-CIX DelhiDelhi, India 109 CtrlS Noida DC1
India AMS-IX MumbaiMumbai, India 86 Sify Rabale - Mumbai
India Extreme IX HyderabadHyderabad, India 24 CtrlS Hyderabad DC1
India NIXI HyderabadHyderabad, India 23 CtrlS Hyderabad DC1
India DE-CIX HyderabadHyderabad, India 14 CtrlS Hyderabad DC1
India MX-IX MumbaiMumbai, India 5 CtrlS Mumbai DC1
Facilities (4)

The buildings SP-iXP Route Servers lists in PeeringDB, and how many of the exchanges in each it's on.

India CtrlS Hyderabad DC1Hyderabad 0 of 3
India CtrlS Noida DC1Noida 0 of 3
India Sify Rabale - MumbaiNavi Mumbai 0 of 3
India CtrlS Mumbai DC1Mumbai 0 of 2