ixreport

Datum Cloud

AS33438

Datum Technology, Inc.

3Exchanges
3On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
SelectivePeering policy
0Using the route servers
3To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with Datum Cloud? · Where should Datum Cloud peer next? · Compare Datum Cloud with another network

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

PeeringDB fix list Printable page · CSV

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

Make the changes on Datum Cloud'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 (3)

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

  1. Brazil IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil · PeeringDB 177From 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.

  2. 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.

  3. United States STLIX Saint Louis, MO, United States · PeeringDB 2585From its IX-F export and website members list
    IPv4206.83.12.48
    IPv62001:504:98::48
    Speed100000 Mbps (100G)
    RS peerNot published

Exchanges over time

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

Map

Where Datum Cloud'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 100G, at the 1 of 3 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 Not in PeeringDB
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil Not in PeeringDB
United States STLIX Saint Louis, MO, United States 206.83.12.48 2001:504:98::48 100G Not in PeeringDB

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

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

United States DE-CIX DallasDallas, United States 177 DataBank Dallas (DFW1)
United States MegaIX DallasDallas, United States 30 DataBank Dallas (DFW1)
United States DFW-IXDallas, United States 11 DataBank Dallas (DFW1)
United States MUS-IXDallas, TX, United States 11 DataBank Dallas (DFW1)
Facilities (1)

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

United States DataBank Dallas (DFW1)Dallas 0 of 4