ixreport

Sano Komunikasi

AS131713 · SPICELINK

PT Sano Komunikasi

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

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

This network elsewhere: the registry history of AS131687-AS131786, the block AS131713 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on Sano Komunikasi'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 Sano Komunikasi's PeeringDB record. Add one entry per connection with these values.

  1. Indonesia JinIX Gianyar, Indonesia · PeeringDB 3495From its IX-F export
    IPv4103.122.64.51
    IPv6–
    SpeedNot published
    RS peerYes

Correct these entries (2)

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
    Port speed differs10G1G
    • In the entry with IPv4 123.108.8.225: set Speed to 1000 (1G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export119.11.184.161 119.11.186.19119.11.186.19
    IPv6 address in PeeringDB, not in the export2404:c8:0:a:0:13:1713:1 2404:c8:0:a:0:13:1713:22404:c8:0:a:0:13:1713:2
    Port speed differs2 × 10G10G
    • The entry with IPv4 119.11.184.161, IPv6 2404:c8:0:a:0:13:1713:1 isn't in the export: delete it if that connection is gone.

Exchanges over time

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

Map

Where Sano Komunikasi'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 43G, at the 6 of 7 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Indonesia EdgeNXT Jakarta, Indonesia 103.61.232.130 2001:df1:d440:1::130 10G Yes PeeringDB
Indonesia IIX-Bali Denpasar, Indonesia 218.100.33.4 1G Yes PeeringDB
Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.8.225 2001:7fa:2:5::e1 10G Yes Both Speed differs
Indonesia JinIX Gianyar, Indonesia 103.122.64.51 Yes Not in PeeringDB
Indonesia JKT-IX Jakarta, Indonesia 119.11.184.161
119.11.186.19
2404:c8:0:a:0:13:1713:1
2404:c8:0:a:0:13:1713:2
2 × 10G Yes Both IPv4 not in exportIPv6 not in exportSpeed differs
Indonesia JKT-IX Bali Denpasar, Indonesia 119.11.192.161 1G Yes PeeringDB
Indonesia OpenIXP / NiCE Indonesia, Indonesia 218.100.27.165 2001:7fa:f::278 1G Yes PeeringDB

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

These exchanges have a switch in a facility where Sano Komunikasi lists itself in PeeringDB, but don't have Sano Komunikasi 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 Datacenter APJII-Cyber
Indonesia CXC JakartaJakarta, Indonesia 201 Datacenter APJII-Cyber
Indonesia BIX JakartaJakarta, Indonesia 180 Datacenter APJII-Cyber
Indonesia DE-CIX JakartaJakarta, Indonesia 177 Datacenter APJII-Cyber
Singapore DE-CIX ASEANSingapore, Singapore 140 Datacenter APJII-Cyber
Indonesia ILIXSurabaya, Indonesia 122 Datacenter APJII-Cyber
Indonesia CDIXJakarta, Indonesia 84 Cyber Data Center International Jakarta
Indonesia Transhybrid IX NetworkJakarta, Indonesia 63 Cyber Data Center International Jakarta; Datacenter APJII-Cyber
Indonesia CXC DenpasarDenpasar, Indonesia 52 CNI DC DPS
Indonesia CENTRO-IXPekanbaru - Jakarta, Indonesia 39 Datacenter APJII-Cyber
Indonesia CNI-IXJakarta, Indonesia 18 Datacenter APJII-Cyber; CNI DC DPS
Indonesia Metta-IXJakarta, Indonesia 16 Datacenter APJII-Cyber
Indonesia GPMIXLampung Timur, Indonesia 13 Datacenter APJII-Cyber
Indonesia JDXJakarta, Indonesia 13 Datacenter APJII-Cyber
Indonesia BatamIX JakartaJakarta, Indonesia 7 Datacenter APJII-Cyber
Indonesia SONIA IXJakarta & Sidoarjo, Indonesia 4 Cyber Data Center International Jakarta
Indonesia Super Internet eXchange (SIX)Bogor, Indonesia 4 Datacenter APJII-Cyber
Indonesia ABS-IXJAKARTA, Indonesia 3 Datacenter APJII-Cyber
Facilities (3)

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

Indonesia Datacenter APJII-CyberJakarta Selatan 2 of 17
Indonesia CNI DC DPSBali 2 of 4
Indonesia Cyber Data Center International JakartaJakarta Selatan 0 of 3