ixreport

SECW TELECOM

AS266409 · SECW

4Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
3Using the route servers
1To fix in PeeringDB
5Facilities in PeeringDB

Tools: Where can I peer with SECW TELECOM? · Where should SECW TELECOM peer next? · Compare SECW TELECOM with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in SECW TELECOM's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

Make the changes on SECW 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 (1)

On the exchange's own member list, but not in SECW TELECOM's PeeringDB record. Add one entry per connection with these values.

  1. Brazil IX.br (PTT.br) Curitiba Curitiba, Brazil · PeeringDB 174From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Exchanges over time

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

Map

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

Brazil Equinix São Paulo São Paulo, Brazil 64.191.233.217 2001:504:0:7:0:26:6409:1 100G Yes PeeringDB
Brazil IX.br (PTT.br) Brasília Brasília/DF, Brazil 45.184.144.125 2001:12f8:0:13::125 100G 3 routes PeeringDB only
Brazil IX.br (PTT.br) Curitiba Curitiba, Brazil Not in PeeringDB
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil 187.16.221.6 2001:12f8::221:6 200G 179 routes Both

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

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

Facilities (5)

The buildings SECW TELECOM 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 SP1 - São PauloSão Paulo 2 of 4
Brazil Equinix SP2 - São PauloBarueri 2 of 4
Brazil DC MATRIX INTERNET S.ASão Paulo 0 of 1
Brazil PIX G8 BrasíliaBrasília 1 of 1