ixreport

Exabit

AS151521 · ExaBit

PT. EXABIT GROUP NETWORK

5Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
5Using the route servers
2To fix in PeeringDB
4Facilities in PeeringDB

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

This network elsewhere: the registry history of AS151502-AS151601, the block AS151521 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in Exabit's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Exabit'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 (1)

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

  1. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476From its IX-F export
    IPv4119.11.187.13
    IPv6–
    Speed1000 Mbps (1G)
    RS peerYes

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 IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:2:5::3f2
    • In the entry with IPv4 123.108.11.226: set IPv6 to 2001:7fa:2:5::3f2 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

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

In the last 30 days Exabit joined 1 exchange and left 0. Growing networks

Joined

  • JDX Jakarta Nov 9, 2026 PeeringDB only

Map

Where Exabit'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 23G across 5 exchanges.

Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.11.226 1G Yes Both IPv6 not in PeeringDB
Indonesia JDX Jakarta, Indonesia 203.29.27.251 10G Yes PeeringDB
Indonesia JKT-IX Jakarta, Indonesia 119.11.187.13
119.11.193.13
1G Yes Not in PeeringDB
Indonesia ODIX Omadata Surabaya, Indonesia 218.100.74.153 10G Yes PeeringDB
Indonesia OpenIXP / NiCE Indonesia, Indonesia 43.252.147.94 1G Yes PeeringDB

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

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

Indonesia IDC 3DJakarta Selatan 2 of 12
Indonesia NTT Jakarta 2 Data Center (JKT2)Jakarta 2 of 12
Indonesia OMADATA - E1 - SUBSurabaya 2 of 7
Indonesia Datacenter APJII-Cyber JAKARTAJakarta 0 of 4

Recent changes Search them

  • Nov 9, 2026 [PDB] AS151521 Exabit added to JDX