ixreport

Brisanet Servicos de Telecomunicacoes: PeeringDB fix list

AS28126 · peeringdb.com/net/5911

PeeringDB

4 things to fix in Brisanet Servicos de Telecomunicacoes's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Brisanet Servicos de Telecomunicacoes'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 Brisanet Servicos de Telecomunicacoes's PeeringDB record. Add one entry per connection with these values.

  1. Brazil IX.br (PTT.br) Salvador Salvador/BA, Brazil · PeeringDB 556From 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.

  2. Brazil IX.br (PTT.br) Teresina Teresina/PI, Brazil · PeeringDB 2078From 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.

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.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs15G100G
    • In the entry with IPv4 80.81.195.194: set Speed to 100000 (100G) (now 15000).
  2. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs15G100G
    • In the entry with IPv4 206.82.105.34: set Speed to 100000 (100G) (now 15000).

From ixreport.com/net/28126/: 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.