G8: PeeringDB fix list
AS28329 · peeringdb.com/net/3861
6 things to fix in G8's PeeringDB record, from what its exchanges publish: 4 to add, 2 to check. As of 2026-10-08 21:56 UTC.
Make the changes on G8'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 (4)
On the exchange's own member list, but not in G8'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.
-
IX.br (PTT.br) Brasília Brasília/DF, Brazil · PeeringDB 178From its IX-F export and website members listThe exchange's IX-F export and website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil · PeeringDB 177From its IX-F export and website members list
The exchange's IX-F export and website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Check these entries (2)
In PeeringDB, but on none of the exchange's own lists. If G8 has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 195.66.227.107 IPv6 2001:7f8:4::6ea9:1 Speed 10000 Mbps (10G) -
IPv4 198.32.160.231 IPv6 2001:504:1::a502:8329:1 Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/28329/: 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.