M-ROOT DNS Server: PeeringDB fix list

AS7500 · peeringdb.com/net/825

PeeringDB

9 things to fix in M-ROOT DNS Server's PeeringDB record, from what its exchanges publish: 3 to add, 3 to correct, 2 to check, 1 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.

Make the changes on M-ROOT DNS Server'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 (3)

On the exchange's own member list, but not in M-ROOT DNS Server's PeeringDB record. Add one entry per connection with these values.

  1. Bhutan btIX Thimphu, Bhutan · PeeringDB 2355From its IX-F export and website members list
    IPv4103.129.62.24
    IPv62001:dea:4000::7500:1
    Speed1000 Mbps (1G)
    RS peerYes

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

  2. Australia IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  3. Pakistan PKIX Lahore Lahore, Pakistan · PeeringDB 3743From its IX-F export

    2 connections, so 2 entries:

    IPv4–
    IPv62001:db8::90
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4–
    IPv62001:db8::91
    Speed10000 Mbps (10G)
    RS peerYes

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

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.

  1. Thailand BKNIX (Thailand) Bangkok, Thailand · PeeringDB 1025
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 203.159.68.23: 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.

  2. Philippines GetaFIX Cebu Cebu, Philippines · PeeringDB 3558
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 116.89.244.18: 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.

  3. Australia IX Australia Brisbane (QLD-IX) Brisbane, Australia · PeeringDB 576
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 218.100.76.115: 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.

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If M-ROOT DNS Server has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Japan JPIX TOKYO Tokyo, Japan · PeeringDB 30Not on its website members list
    IPv4210.171.224.5
    IPv62001:de8:8::7500:1
    Speed1000 Mbps (1G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

  2. Malaysia MyIX Kuala Lumpur, Malaysia · PeeringDB 250Not on its website members list
    IPv4218.100.44.40
    IPv62001:de8:10::28
    Speed1000 Mbps (1G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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. Japan NSPIXP3ghost Osaka, Japan · PeeringDB 234

    Only the operator's own networks

    IPv4202.249.38.1
    IPv62001:200:0:fe10::1d4c:0
    Speed1000 Mbps (1G)

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