NETRUN TECHNOLOGIES: PeeringDB fix list
AS59185 · peeringdb.com/net/8660
4 things to fix in NETRUN TECHNOLOGIES's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 2 to check. As of 2026-10-08 20:58 UTC.
Make the changes on NETRUN TECHNOLOGIES'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 (1)
On the exchange's own member list, but not in NETRUN TECHNOLOGIES's PeeringDB record. Add one entry per connection with these values.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
Correct these entries (1)
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 10G 2 × 10G PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
Check these entries (2)
In PeeringDB, but on none of the exchange's own lists. If NETRUN TECHNOLOGIES has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 103.184.198.155 IPv6 2400:d180:72::c5 Speed 10000 Mbps (10G) -
IPv4 103.77.110.17 IPv6 – Speed 10000 Mbps (10G) IPv4 103.77.110.23 IPv6 2001:df2:1900:4::23 Speed 10000 Mbps (10G)
From ixreport.com/net/59185/: 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.