ixreport

HELIUM

AS147137 · HELIUM

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

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

This network elsewhere: the registry history of AS147072-AS147171, the block AS147137 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in HELIUM's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on HELIUM'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. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    Port speed differs10G5G
    • In the entry with IPv4 119.11.185.82: set Speed to 5000 (5G) (now 10000).

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 HELIUM'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 30G across 3 exchanges.

Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.8.100 2001:7fa:2:5::64 10G Yes Both
Indonesia JKT-IX Jakarta, Indonesia 119.11.185.82 2404:c8:0:a:0:14:7137:1 10G Yes Both Speed differs
Indonesia OpenIXP / NiCE Indonesia, Indonesia 43.252.147.103 2001:7fa:f::595 10G Yes PeeringDB

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

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

Indonesia Datacenter APJII-CyberJakarta Selatan 2 of 17
Indonesia IDC 3DJakarta Selatan 1 of 12
Indonesia NTT Jakarta 2 Data Center (JKT2)Jakarta 2 of 12
Indonesia ProDCJakarta Selatan 0 of 2