NLINK: PeeringDB fix list
AS28585 · peeringdb.com/net/31621
9 things to fix in NLINK's PeeringDB record, from what its exchanges publish: 9 to add. As of 2026-10-08 18:53 UTC.
Make the changes on NLINK'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 (9)
On the exchange's own member list, but not in NLINK'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.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IX.br (PTT.br) Porto Alegre Porto Alegre/RS, Brazil · PeeringDB 173From 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 website members list 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 website members list
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
From ixreport.com/net/28585/: 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.