Netstra Communications: PeeringDB fix list
AS137654 · peeringdb.com/net/20781
3 things to fix in Netstra Communications's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Netstra Communications'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 (2)
On the exchange's own member list, but not in Netstra Communications's PeeringDB record. Add one entry per connection with these values.
-
IPv4 103.77.108.32 IPv6 2001:df2:1900:2::32 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.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
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 Address belongs to another network in PeeringDB 103.77.108.32 is AS136636 Sharplink Wireless Solution 103.77.108.32 Address belongs to another network in PeeringDB 2001:df2:1900:2::32 is AS136636 Sharplink Wireless Solution 2001:df2:1900:2::32 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
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/137654/: 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.