DBYTE FACILITY NLD: PeeringDB fix list

AS153756 · peeringdb.com/net/40010

PeeringDB

2 things to fix in DBYTE FACILITY NLD's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 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).

From ixreport.com/net/153756/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.