ixreport

SIGMA

AS153155 · SIGMA

PT Sigma Data Nusa

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

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

This network elsewhere: the registry history of AS153059-AS153158, the block AS153155 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on SIGMA'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 DE-CIX Jakarta Jakarta, Indonesia · PeeringDB 4411
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 49.213.56.175: set Speed to 1000 (1G) (now 10000).

Check these entries (1)

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

  1. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476Not on its IX-F export
    IPv4119.11.187.150
    IPv6–
    Speed10000 Mbps (10G)

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, 20265
Nov 7, 20265
Nov 6, 20265
Nov 5, 20265
Nov 4, 20265
Nov 3, 20265
Nov 2, 20265
Nov 1, 20265
Oct 31, 20265
Oct 30, 20265
Oct 29, 20265
Oct 28, 20265
Oct 27, 20265
Oct 26, 20265
Oct 25, 20265
Oct 24, 20265
Oct 23, 20265
Oct 22, 20265
Oct 21, 20265
Oct 20, 20265
Oct 19, 20265
Oct 18, 20265
Oct 17, 20265
Oct 16, 20265
Oct 15, 20265
Oct 14, 20265
Oct 13, 20265
Oct 12, 20265
Oct 11, 20265
Oct 10, 20265
Oct 9, 20265
Oct 8, 20265
Oct 7, 20265
Oct 6, 20265
Oct 5, 20265
Oct 4, 20265
Oct 3, 20265

Map

Where SIGMA'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 50G across 5 exchanges.

Indonesia DE-CIX Jakarta Jakarta, Indonesia 49.213.56.175 2001:df5:7880:0:2:5643:0:1 10G 1 routes Both Speed differs
Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.11.234 2001:7fa:2:5::3fa 10G Yes Both
Indonesia JKT-IX Jakarta, Indonesia 119.11.187.150 10G Yes PeeringDB only
Indonesia ODIX Omadata Surabaya, Indonesia 218.100.74.175 2403:1a00::eb 10G PeeringDB
Indonesia OpenIXP / NiCE Indonesia, Indonesia 43.252.147.111 10G PeeringDB

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

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

Indonesia OMNIIX INDONESIABatam, Jakarta, Indonesia 111 OMADATA - E1 - SUB
Indonesia Transhybrid IX NetworkJakarta, Indonesia 63 OMADATA - E1 - SUB
Indonesia JKT-IX SurabayaSurabaya, Indonesia 59 OMADATA - E1 - SUB
Indonesia CXC SurabayaSurabaya, Indonesia 9 OMADATA - E1 - SUB
Indonesia SONIA IXJakarta & Sidoarjo, Indonesia 4 OMADATA - E1 - SUB
Facilities (1)

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

Indonesia OMADATA - E1 - SUBSurabaya 2 of 7