ixreport

Brisanet Servicos de Telecomunicacoes

AS28126

15Exchanges
2On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
14Using the route servers
4To fix in PeeringDB
9Facilities in PeeringDB

Tools: Where can I peer with Brisanet Servicos de Telecomunicacoes? · Where should Brisanet Servicos de Telecomunicacoes peer next? · Compare Brisanet Servicos de Telecomunicacoes with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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-11-19 12:40 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).

Exchanges over time

051015Oct 3, 2026Nov 19, 202615
Show as a table
DateExchanges
Nov 19, 202615
Nov 18, 202615
Nov 17, 202615
Nov 16, 202615
Nov 15, 202615
Nov 14, 202615
Nov 13, 202615
Nov 12, 202615
Nov 11, 202615
Nov 10, 202615
Nov 9, 202615
Nov 8, 202615
Nov 7, 202615
Nov 6, 202615
Nov 5, 202615
Nov 4, 202615
Nov 3, 202615
Nov 2, 202615
Nov 1, 202615
Oct 31, 202615
Oct 30, 202615
Oct 29, 202615
Oct 28, 202615
Oct 27, 202615
Oct 26, 202615
Oct 25, 202615
Oct 24, 202615
Oct 23, 202615
Oct 22, 202615
Oct 21, 202615
Oct 20, 202615
Oct 19, 202615
Oct 18, 202615
Oct 17, 202615
Oct 16, 202615
Oct 15, 202615
Oct 14, 202615
Oct 13, 202615
Oct 12, 202615
Oct 11, 202615
Oct 10, 202615
Oct 9, 202615
Oct 8, 202615
Oct 7, 202615
Oct 6, 202615
Oct 5, 202615
Oct 4, 202615
Oct 3, 202613

Map

Where Brisanet Servicos de Telecomunicacoes's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 1.1T, at the 13 of 15 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.195.194 2001:7f8::6dde:0:1 15G 13 routes Both Speed differs
United States DE-CIX New York New York, United States 206.82.105.34 2001:504:36::6dde:0:2 15G 13 routes Both Speed differs
Brazil DE-CIX Rio de Janeiro Rio de Janeiro, Brazil 45.68.93.15 2801:81:c0:2:0:6dde:0:1 100G 515 routes Both
Brazil DE-CIX Sao Paulo Sao Paulo, Brazil 45.68.92.38 2801:81:c0:1:0:6dde:0:1 100G Down Both
Brazil IX.br (PTT.br) Aracaju Aracaju/SE, Brazil 200.219.130.54 2001:12f8:0:1::54 10G 66 routes PeeringDB
Brazil IX.br (PTT.br) Campina Grande Campina Grande/PB, Brazil 200.192.109.32 2001:12f8:0:12::32 10G 19 routes Both
Brazil IX.br (PTT.br) Fortaleza Fortaleza/CE, Brazil 45.68.72.125
45.68.73.232
45.68.74.135
2001:12f8:0:9::125
2001:12f8:0:9::145:232
2001:12f8:0:9::146:135
3 × 100G 1,860 routes Both
Brazil IX.br (PTT.br) João Pessoa João Pessoa/PB, Brazil 187.16.193.26 2001:12f8:0:16::26 10G 92 routes Both
Brazil IX.br (PTT.br) Maceió Maceió/AL, Brazil 45.227.1.36 2001:12f8:0:31::36 10G 94 routes Both
Brazil IX.br (PTT.br) Natal Natal/RN, Brazil 187.16.196.43 2001:12f8:0:19::43 10G 160 routes Both
Brazil IX.br (PTT.br) Recife Recife/PE, Brazil 200.219.147.88 2001:12f8:0:10::88 10G 116 routes PeeringDB only
Brazil IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil 45.68.80.99
45.68.82.221
2001:12f8:0:2::99
2001:12f8:0:2::54:221
2 × 100G 1,265 routes Both
Brazil IX.br (PTT.br) Salvador Salvador/BA, Brazil 77 routes Website list only
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil 187.16.208.36
187.16.209.120
187.16.221.32
2001:12f8::208:36
2001:12f8::209:120
2001:12f8::221:32
3 × 100G 1,896 routes Both
Brazil IX.br (PTT.br) Teresina Teresina/PI, Brazil 59 routes Website list only

Exchanges in its buildings that it isn't on (6)

These exchanges have a switch in a facility where Brisanet Servicos de Telecomunicacoes lists itself in PeeringDB, but don't have Brisanet Servicos de Telecomunicacoes as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Facilities (9)

The buildings Brisanet Servicos de Telecomunicacoes lists in PeeringDB, and how many of the exchanges in each it's on.

Brazil Equinix SP4 - São PauloBarueri 2 of 6
Brazil Equinix RJ2 - Rio de JaneiroRio de Janeiro 2 of 5
Brazil Equinix SP2 - São PauloBarueri 1 of 4
Brazil AngoNAP FortalezaFortaleza 1 of 2
Brazil Cirion Sao Paulo - SAO1Cotia 1 of 2
Brazil Tecto TFOR1/2 (ex Globenet CLS & Big Lobster)Fortaleza 1 of 2
Brazil Cirion FortalezaFortaleza 1 of 1
Brazil Cirion Rio de Janeiro - RIO1Rio de Janeiro 1 of 1
Brazil Telxius Fortaleza DCFortaleza 1 of 1