ixreport

ATEL TELECOM

AS262468 · ATEL TELECOM

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on ATEL 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 ATEL TELECOM'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.

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, 20263

Map

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

Brazil IX.br (PTT.br) Fortaleza Fortaleza/CE, Brazil 45.68.72.108
45.68.72.155
2001:12f8:0:9::108
2001:12f8:0:9::155
100G + 20G 526 routes Both
Brazil IX.br (PTT.br) Recife Recife/PE, Brazil 200.219.147.75 2001:12f8:0:10::75 10G 262 routes Both
Brazil IX.br (PTT.br) Salvador Salvador/BA, Brazil 263 routes Website list only
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil 187.16.221.18 2001:12f8::221:18 100G 263 routes Both

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

These exchanges have a switch in a facility where ATEL TELECOM lists itself in PeeringDB, but don't have ATEL 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 ATEL TELECOM lists in PeeringDB, and how many of the exchanges in each it's on.

Brazil Equinix SP4 - São PauloBarueri 1 of 6
Brazil Tecto TFOR1/2 (ex Globenet CLS & Big Lobster)Fortaleza 1 of 2
Brazil BR.Digital Fortaleza (FLA1)Fortaleza 1 of 1
Brazil BR.Digital Recife (RCE1)Recife 1 of 1
Brazil Cirion FortalezaFortaleza 1 of 1
Brazil PIX DTEL RECIFERecife 1 of 1