SYMPHONY THAI - IP Transit: PeeringDB fix list
AS132876 · peeringdb.com/net/6186
5 things to fix in SYMPHONY THAI - IP Transit's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on SYMPHONY THAI - IP Transit'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 SYMPHONY THAI - IP Transit's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
DE-CIX New York New York, United States · PeeringDB 804From its IX-F export and website members list
IPv4 206.82.105.64 IPv6 2001:504:36:0:2:70c:0:1 Speed 10000 Mbps (10G) RS peer Yes
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 IPv4 address missing from PeeringDB 80.81.194.146 80.81.194.146 80.81.197.64 IPv6 address missing from PeeringDB 2001:7f8::2:70c:0:1 2001:7f8::2:70c:0:1 2001:7f8::2:70c:0:2 Port speed differs 200G 2 × 200G - Add an entry: IPv4 80.81.197.64, IPv6 2001:7f8::2:70c:0:2, speed 200000 (200G), RS peer yes.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 206.82.105.64 is AS20340 Calltower 206.82.105.64 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.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If SYMPHONY THAI - IP Transit 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.225.233 IPv6 2001:de8:8::13:2876:1 Speed 1000 Mbps (1G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/132876/: 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.