ixreport

datamena

AS57187 · EITC-datamena

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

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

Make the changes on datamena'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 Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.8.17 185.1.8.104185.1.8.17 185.1.8.104 185.1.8.135
    IPv6 address missing from PeeringDB2001:7f8:73::df63:0:2 2001:7f8:73::df63:0:32001:7f8:73::df63:0:1 2001:7f8:73::df63:0:2 2001:7f8:73::df63:0:3
    Port speed differs2 × 100G3 × 200G
    • In the entry with IPv4 185.1.8.104: set Speed to 200000 (200G) (now 100000).
    • In the entry with IPv4 185.1.8.17: set Speed to 200000 (200G) (now 100000).
    • Add an entry: IPv4 185.1.8.135, IPv6 2001:7f8:73::df63:0:1, speed 200000 (200G), RS peer no.

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, 20262
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 datamena'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 240G across 2 exchanges.

United Arab Emirates SH-IX Fujairah, United Arab Emirates 185.1.15.54
185.1.15.64
2001:7f8:7a::5:7187:1
2001:7f8:7a::5:7187:2
2 × 20G Both
United Arab Emirates UAE-IX Dubai, United Arab Emirates 185.1.8.17
185.1.8.104
2001:7f8:73::df63:0:2
2001:7f8:73::df63:0:3
2 × 100G 256 routes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs

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

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

Bulgaria NetIXSofia, Bulgaria 204 Equinix DX1 - Dubai; datamena DXA - Dubai
Facilities (2)

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

United Arab Emirates datamena DXA - DubaiDubai 1 of 2
United Arab Emirates Equinix DX1 - DubaiDubai 1 of 2