ixreport

Oops Telecom

AS28624 · OOPS

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

Tools: Where can I peer with Oops Telecom? · Where should Oops Telecom peer next? · Compare Oops Telecom with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in Oops Telecom's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-11-19 12:40 UTC.

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

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

Exchanges over time

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

Map

Where Oops Telecom'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 220G, at the 4 of 6 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Brazil IX.br (PTT.br) Aracaju Aracaju/SE, Brazil 200.219.130.17 2001:12f8:0:1::17 10G 214 routes PeeringDB
Brazil IX.br (PTT.br) Fortaleza Fortaleza/CE, Brazil 45.68.72.187 2001:12f8:0:9::187 100G 94 routes Both
Brazil IX.br (PTT.br) Maceió Maceió/AL, Brazil 45.227.1.19 2001:12f8:0:31::19 10G 214 routes Both
Brazil IX.br (PTT.br) Recife Recife/PE, Brazil Down Website list only
Brazil IX.br (PTT.br) Salvador Salvador/BA, Brazil 214 routes Not in PeeringDB
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil 187.16.216.103 2001:12f8::103 100G 214 routes Both

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

These exchanges have a switch in a facility where Oops Telecom lists itself in PeeringDB, but don't have Oops Telecom 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.

Bulgaria NetIXSofia, Bulgaria 204 Eletronet - Sao Paulo
Facilities (2)

The buildings Oops Telecom lists in PeeringDB, and how many of the exchanges in each it's on.

Brazil Eletronet - Sao PauloSão Paulo 1 of 2
Brazil BR.Digital Fortaleza (FLA1)Fortaleza 1 of 1