DE-CIX Mumbai Route Servers
AS59200 · DE-CIX Mumbai
DE-CIX Interwire Internet Services Pvt Ltd
Tools: Where can I peer with DE-CIX Mumbai Route Servers? · Where should DE-CIX Mumbai Route Servers peer next? · Compare DE-CIX Mumbai Route Servers with another network
This network elsewhere: the registry history of AS59161-AS59200, the block AS59200 is in, on RIR Tracker
PeeringDB fix list Printable page · CSV
5 things to fix in DE-CIX Mumbai Route Servers's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on DE-CIX Mumbai 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.
Add these exchanges (2)
On the exchange's own member list, but not in DE-CIX Mumbai Route Servers's PeeringDB record. Add one entry per connection with these values.
-
2 connections, so 2 entries:
IPv4 103.228.174.64 IPv6 2400:d180:68::64 Speed 1000 Mbps (1G) RS peer No IPv4 103.228.174.65 IPv6 2400:d180:68::65 Speed 1000 Mbps (1G) RS peer No -
2 connections, so 2 entries:
IPv4 103.27.168.64 IPv6 2400:d180:67::64 Speed 1000 Mbps (1G) RS peer No IPv4 103.27.168.65 IPv6 2400:d180:67::65 Speed 1000 Mbps (1G) RS peer No
Correct these entries (3)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 103.228.174.64 is AS24470 DE-CIX Chennai Route Servers 103.228.174.64 Address belongs to another network in PeeringDB 103.228.174.65 is AS24470 DE-CIX Chennai Route Servers 103.228.174.65 Address belongs to another network in PeeringDB 2400:d180:68::64 is AS24470 DE-CIX Chennai Route Servers 2400:d180:68::64 Address belongs to another network in PeeringDB 2400:d180:68::65 is AS24470 DE-CIX Chennai Route Servers 2400:d180:68::65 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 103.27.168.64 is AS24457 DE-CIX Delhi Route Servers 103.27.168.64 Address belongs to another network in PeeringDB 103.27.168.65 is AS24457 DE-CIX Delhi Route Servers 103.27.168.65 Address belongs to another network in PeeringDB 2400:d180:67::64 is AS24457 DE-CIX Delhi Route Servers 2400:d180:67::64 Address belongs to another network in PeeringDB 2400:d180:67::65 is AS24457 DE-CIX Delhi Route Servers 2400:d180:67::65 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
-
Problem PeeringDB has The export has IPv4 address in PeeringDB, not in the export 103.27.170.64 103.27.170.65 103.27.170.64 IPv6 address in PeeringDB, not in the export 2401:7500:fff6::64 2401:7500:fff6::65 2401:7500:fff6::64 Port speed differs 2 × 1G 10G - In the entry with IPv4 103.27.170.64: set Speed to 10000 (10G) (now 1000).
- The entry with IPv4 103.27.170.65, IPv6 2401:7500:fff6::65 isn't in the export: delete it if that connection is gone.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 3 |
| Nov 18, 2026 | 3 |
| Nov 17, 2026 | 3 |
| Nov 16, 2026 | 3 |
| Nov 15, 2026 | 3 |
| Nov 14, 2026 | 3 |
| Nov 13, 2026 | 3 |
| Nov 12, 2026 | 3 |
| Nov 11, 2026 | 3 |
| Nov 10, 2026 | 3 |
| Nov 9, 2026 | 3 |
| Nov 8, 2026 | 3 |
| Nov 7, 2026 | 3 |
| Nov 6, 2026 | 3 |
| Nov 5, 2026 | 3 |
| Nov 4, 2026 | 3 |
| Nov 3, 2026 | 3 |
| Nov 2, 2026 | 3 |
| Nov 1, 2026 | 3 |
| Oct 31, 2026 | 3 |
| Oct 30, 2026 | 3 |
| Oct 29, 2026 | 3 |
| Oct 28, 2026 | 3 |
| Oct 27, 2026 | 3 |
| Oct 26, 2026 | 3 |
| Oct 25, 2026 | 3 |
| Oct 24, 2026 | 3 |
| Oct 23, 2026 | 3 |
| Oct 22, 2026 | 3 |
| Oct 21, 2026 | 3 |
| Oct 20, 2026 | 3 |
| Oct 19, 2026 | 3 |
| Oct 18, 2026 | 3 |
| Oct 17, 2026 | 3 |
| Oct 16, 2026 | 3 |
| Oct 15, 2026 | 3 |
| Oct 14, 2026 | 3 |
| Oct 13, 2026 | 3 |
| Oct 12, 2026 | 3 |
| Oct 11, 2026 | 3 |
| Oct 10, 2026 | 3 |
| Oct 9, 2026 | 3 |
| Oct 8, 2026 | 3 |
| Oct 7, 2026 | 3 |
| Oct 6, 2026 | 3 |
| Oct 5, 2026 | 3 |
| Oct 4, 2026 | 3 |
| Oct 3, 2026 | 3 |
Map
Where DE-CIX Mumbai 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.
| DE-CIX Chennai Chennai, India | 1G | Not in PeeringDB Address taken | |
| DE-CIX Delhi Delhi, India | 1G | Not in PeeringDB Address taken | |
| DE-CIX Mumbai Mumbai, India | 2 × 1G | Both IPv4 not in exportIPv6 not in exportSpeed differs |
These exchanges have a switch in a facility where DE-CIX Mumbai Route Servers lists itself in PeeringDB, but don't have DE-CIX Mumbai 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.
| Extreme IX MumbaiMumbai, India | 246 | |
| NetIXSofia, Bulgaria | 204 | |
| NIXI MumbaiMumbai, India | 177 | |
| AMS-IX MumbaiMumbai, India | 86 | |
| Equinix MumbaiMumbai, India | 24 | |
| X3M-IXMumbai, India | 6 | |
| MX-IX MumbaiMumbai, India | 5 |
Facilities (9)
The buildings DE-CIX Mumbai Route Servers lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix MB1 - Mumbai (GPX Mumbai 1)Mumbai | 1 of 7 | |
| Equinix MB2 - Mumbai (GPX Mumbai 2)Mumbai | 1 of 6 | |
| Netmagic Chandivali - MUM-DC05Mumbai | 1 of 4 | |
| STTGDC BOM2Mumbai | 1 of 4 | |
| Web Werks Mumbai 1Mumbai | 1 of 4 | |
| Sify Rabale - MumbaiNavi Mumbai | 1 of 3 | |
| Nxtra Data Mumbai DC 3Mumbai | 1 of 2 | |
| Nxtra Data Mumbai DC 2Mumbai | 1 of 1 | |
| Web Werks Mumbai 2Navi Mumbai, | 1 of 1 |