M-ROOT DNS Server
AS7500
Tools: Where can I peer with M-ROOT DNS Server? · Where should M-ROOT DNS Server peer next? · Compare M-ROOT DNS Server with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
8 things to fix in M-ROOT DNS Server's PeeringDB record, from what its exchanges publish: 3 to add, 2 to correct, 2 to check, 1 at exchanges that look shut down. As of 2026-11-19 12:40 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.
-
IPv4 103.129.62.24 IPv6 2001:dea:4000::7500:1 Speed 1000 Mbps (1G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 – IPv6 2001:db8::90 Speed 10000 Mbps (10G) RS peer Yes 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 (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.
-
Problem PeeringDB has The export has Port speed differs 1G 10G - 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.
-
Problem PeeringDB has The export has Port speed differs 1G 10G - 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.
-
IPv4 210.171.224.5 IPv6 2001:de8:8::7500:1 Speed 1000 Mbps (1G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 218.100.44.40 IPv6 2001:de8:10::28 Speed 1000 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.
-
Only the operator's own networks
IPv4 202.249.38.1 IPv6 2001:200:0:fe10::1d4c:0 Speed 1000 Mbps (1G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 44 |
| Nov 18, 2026 | 44 |
| Nov 17, 2026 | 44 |
| Nov 16, 2026 | 44 |
| Nov 15, 2026 | 44 |
| Nov 14, 2026 | 44 |
| Nov 13, 2026 | 44 |
| Nov 12, 2026 | 44 |
| Nov 11, 2026 | 44 |
| Nov 10, 2026 | 44 |
| Nov 9, 2026 | 44 |
| Nov 8, 2026 | 44 |
| Nov 7, 2026 | 44 |
| Nov 6, 2026 | 44 |
| Nov 5, 2026 | 44 |
| Nov 4, 2026 | 43 |
| Nov 3, 2026 | 44 |
| Nov 2, 2026 | 44 |
| Nov 1, 2026 | 44 |
| Oct 31, 2026 | 44 |
| Oct 30, 2026 | 44 |
| Oct 29, 2026 | 44 |
| Oct 28, 2026 | 44 |
| Oct 27, 2026 | 44 |
| Oct 26, 2026 | 44 |
| Oct 25, 2026 | 44 |
| Oct 24, 2026 | 44 |
| Oct 23, 2026 | 44 |
| Oct 22, 2026 | 44 |
| Oct 21, 2026 | 44 |
| Oct 20, 2026 | 44 |
| Oct 19, 2026 | 44 |
| Oct 18, 2026 | 44 |
| Oct 17, 2026 | 44 |
| Oct 16, 2026 | 44 |
| Oct 15, 2026 | 44 |
| Oct 14, 2026 | 44 |
| Oct 13, 2026 | 44 |
| Oct 12, 2026 | 44 |
| Oct 11, 2026 | 44 |
| Oct 10, 2026 | 44 |
| Oct 9, 2026 | 44 |
| Oct 8, 2026 | 44 |
| Oct 7, 2026 | 44 |
| Oct 6, 2026 | 44 |
| Oct 5, 2026 | 44 |
| Oct 4, 2026 | 44 |
| Oct 3, 2026 | 44 |
Map
Where M-ROOT DNS Server'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.
| AIX Tapos, Depok, Indonesia | 1G | Both | |
| BBIX Singapore Singapore, Singapore | 1G | PeeringDB | |
| BDIX Dhaka, Bangladesh | 1G | PeeringDB | |
| BKNIX (Thailand) Bangkok, Thailand | 1G | Both Speed differs | |
| btIX Thimphu, Bhutan | 1G | Not in PeeringDB | |
| CNX Phnom Penh, Cambodia | 1G | Both | |
| DE-CIX ASEAN Singapore, Singapore | 1G | Both | |
| DE-CIX Jakarta Jakarta, Indonesia | 1G | Both | |
| DIX-IE Tokyo, Japan | 1G | PeeringDB | |
| Equinix Paris Paris, France | 1G | PeeringDB | |
| Equinix Singapore Singapore, Singapore | 1G | PeeringDB | |
| FCIX Fremont, United States | 1G | Both | |
| France-IX Paris Paris, France | 1G | PeeringDB | |
| GetaFIX Cebu Cebu, Philippines | 1G | PeeringDB | |
| HKIX Hong Kong, Hong Kong | 10G | Both | |
| IIX-Jakarta Jakarta, Indonesia | 1G | Both | |
| InterLAN-IX Bucharest, Romania | 1G | Both | |
| IX Australia Brisbane (QLD-IX) Brisbane, Australia | 1G | Both Speed differs | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | Website list only | ||
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | 10G | PeeringDB only | |
| JKT-IX Jakarta, Indonesia | 1G | Both | |
| JPIX OSAKA Osaka, Japan | 1G | PeeringDB | |
| JPIX TOKYO Tokyo, Japan | 1G | PeeringDB only | |
| JPNAP Osaka Osaka, Japan | 1G | PeeringDB | |
| JPNAP Tokyo Tokyo, Japan | 1G | PeeringDB | |
| KINX Seoul, South Korea | 1G | PeeringDB | |
| MARIIX Mangilao, Guam | 1G | Both | |
| MegaIX Bay Area San Francisco, United States | 1G | Both | |
| MegaIX Brisbane Brisbane, Australia | 1G | Both | |
| MISPA-IXP Ulaanbaatar, Mongolia | 1G | PeeringDB | |
| MVIXP Male', Maldives | 1G | PeeringDB | |
| MX-IX Kolkata Kolkata, India | 1G | PeeringDB | |
| MyIX Kuala Lumpur, Malaysia | 1G | PeeringDB only | |
| NIXI Mumbai Mumbai, India | 1G | PeeringDB | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 1G | Both | |
| npIX DH Kathmandu, Nepal | 1G | Both | |
| NSPIXP3ghost Osaka, Japan | 1G | PeeringDB | |
| OpenIXP / NiCE Indonesia, Indonesia | 1G | PeeringDB | |
| PhOpenIX-Manila Manila, Philippines | 1G | PeeringDB | |
| PKIX Lahore Lahore, Pakistan | 10G | Not in PeeringDB | |
| SFINX Paris, France | 1G | PeeringDB | |
| SFMIX San Francisco, United States | 1G | Both | |
| TWIX Taipei, Taiwan | 1G | PeeringDB | |
| VNIX-HN Hanoi, Vietnam | 1G | PeeringDB |
M-ROOT DNS Server lists no facilities in PeeringDB.