ixreport

Direct Telecom

AS264997 · Direct Telecom Ltda

Direct Telecom Ltda

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

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

Make the changes on Direct Telecom's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (1)

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. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs10G500M
    • In the entry with IPv4 195.66.231.165: set Speed to 500 (500M) (now 10000).

Exchanges over time

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

Map

Where Direct 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 560.5G across 9 exchanges.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.211.4 2001:7f8:1:0:a500:26:4997:1 500M Up, 0 routes Both
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.195.169 2001:7f8::4:b2:0:1 100G Up, 0 routes Both
United States DE-CIX New York New York, United States 206.82.105.114 2001:504:36:0:4:b2:0:1 20G Up, 0 routes Both
Brazil IX.br (PTT.br) Brasília Brasília/DF, Brazil 45.184.144.227 2001:12f8:0:13::227 10G 329 routes PeeringDB only
Brazil IX.br (PTT.br) Fortaleza Fortaleza/CE, Brazil 45.68.73.23
45.68.74.120
2001:12f8:0:9::145:23
2001:12f8:0:9::146:120
2 × 100G 658 routes Both
Brazil IX.br (PTT.br) São Luís São Luís/MA, Brazil 45.227.0.71 2001:12f8:0:30::71 10G 329 routes PeeringDB only
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil 187.16.209.113
187.16.211.29
2001:12f8::209:113
2001:12f8::211:29
2 × 100G 329 routes Both
Brazil IX.br (PTT.br) Teresina Teresina/PI, Brazil 200.219.138.15 2001:12f8:0:29::15 10G 329 routes Both
United Kingdom LINX LON1 London, United Kingdom 195.66.231.165 2001:7f8:4::4:b25:1 10G Up, 0 routes Both Speed differs

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

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

The buildings Direct 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 AngoNAP FortalezaFortaleza 1 of 2
Brazil Tecto TFOR1/2 (ex Globenet CLS & Big Lobster)Fortaleza 1 of 2