ixreport

M Alhuda

AS44817 · AS-RHZAHRA

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

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

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If M Alhuda has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Indonesia DE-CIX Jakarta Jakarta, Indonesia · PeeringDB 4411Not on its IX-F export or website members list
    IPv449.213.56.109
    IPv62001:df5:7880::af11:0:1
    Speed10000 Mbps (10G)

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, 20263
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 M Alhuda'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 21G across 3 exchanges.

Indonesia DE-CIX Jakarta Jakarta, Indonesia 49.213.56.109 2001:df5:7880::af11:0:1 10G Down PeeringDB only
Japan Japan Community IX - INIXP Japan, Japan 2401:3fa0::4:4817:1 1G Yes PeeringDB
Denmark NorthIX Copenhagen, Denmark 2001:67c:bec:c7:0:4:4817:1 10G Yes PeeringDB

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

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

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

Singapore Equinix SG1 - SingaporeSingapore 0 of 11
Japan Equinix TY8 - TokyoTokyo 0 of 4
Japan NTT DOCOMO BUSINESS TK1 - Tokyo (NTT Otemachi)Tokyo 0 of 2
Japan NTT Communications - PC1 Ajigaura Landing StationAjigaura No exchange