ixreport

N4U BROADBAND: PeeringDB fix list

AS141865 · peeringdb.com/net/28173

PeeringDB

2 things to fix in N4U BROADBAND's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on N4U BROADBAND'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 Extreme IX Delhi Delhi, India · PeeringDB 1323
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:df2:1900:1::114
    Port speed differs30G40G
    • In the entry with IPv4 45.120.248.114: set IPv6 to 2001:df2:1900:1::114 (now empty); set Speed to 40000 (40G) (now 30000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. India Extreme IX Mumbai Mumbai, India · PeeringDB 1627
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:df2:1900:2::1044
    Port speed differs1G10G
    • In the entry with IPv4 103.77.109.44: set IPv6 to 2001:df2:1900:2::1044 (now empty); set Speed to 10000 (10G) (now 1000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

From ixreport.com/net/141865/: 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.