ixreport

S1 TELECOM

AS265181 · S1 TELECOMUNICAÇOES

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

Tools: Where can I peer with S1 TELECOM? · Where should S1 TELECOM peer next? · Compare S1 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 S1 TELECOM's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

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

  1. Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil · PeeringDB 171From 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

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

Map

Where S1 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 10G, at the 1 of 2 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Brazil IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil 45.68.80.205 2001:12f8:0:2::205 10G Down Both
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil Not in PeeringDB

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

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

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

Brazil Equinix RJ2 - Rio de JaneiroRio de Janeiro 1 of 5
Brazil Equinix SP2 - São PauloBarueri 1 of 4
Brazil Elea RJO1 - Rio de JaneiroRio de Janeiro 1 of 3
Brazil Cirion Rio de Janeiro - RIO1Rio de Janeiro 1 of 1
Brazil Datacenter UFINET BRASIL (Novo Teleporto)Rio de Janeiro 1 of 1
Brazil Teleporto Rio de JaneiroRio de Janeiro 1 of 1