ixreport

DBYTE FACILITY NLD

AS153756 · Dbyte

DBYTE FACILITY NETWORK PRIVATE LIMITED

3Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
3Using the route servers
2To fix in PeeringDB
11Facilities in PeeringDB

Tools: Where can I peer with DBYTE FACILITY NLD? · Where should DBYTE FACILITY NLD peer next? · Compare DBYTE FACILITY NLD with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in DBYTE FACILITY NLD's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on DBYTE FACILITY NLD's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (2)

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.

  1. India DE-CIX Delhi Delhi, India · PeeringDB 2587
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export103.27.168.37none
    IPv6 address in PeeringDB, not in the export2400:d180:67::37none
    Port speed differs100G10G
    • The entry with IPv4 103.27.168.37, IPv6 2400:d180:67::37 isn't in the export: delete it if that connection is gone.
  2. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G + 1G
    • In the entry with IPv4 103.27.171.213: set Speed to 1000 (1G) (now 100000).

Exchanges over time

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

Map

Where DBYTE FACILITY NLD'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 210G across 3 exchanges.

India DE-CIX Delhi Delhi, India 103.27.168.37 2400:d180:67::37 100G Yes Both IPv4 not in exportIPv6 not in exportSpeed differs
India DE-CIX Mumbai Mumbai, India 103.27.171.213 2401:7500:fff6::13c 100G Yes Both Speed differs
India Extreme IX Delhi Delhi, India 45.120.248.118 2001:df2:1900:1::118 10G Yes PeeringDB

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

These exchanges have a switch in a facility where DBYTE FACILITY NLD lists itself in PeeringDB, but don't have DBYTE FACILITY NLD 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.

Facilities (11)

The buildings DBYTE FACILITY NLD lists in PeeringDB, and how many of the exchanges in each it's on.

India Equinix MB1 - Mumbai (GPX Mumbai 1)Mumbai 1 of 7
India Sify Greenfort - NoidaNoida 2 of 7
India Equinix MB2 - Mumbai (GPX Mumbai 2)Mumbai 1 of 6
India TATA Communications GK1New Delhi 2 of 6
India STTGDC BOM2Mumbai 1 of 4
India STTGDC DEL3Delhi 2 of 4
India CtrlS Noida DC1Noida 2 of 3
India STTGDC CHN1Chennai 0 of 3
India STTGDC DEL1Delhi 0 of 2
India CtrlS Lucknow DC1Lucknow 0 of 1
India CtrlS Patna DC1Patna 0 of 1