ixreport

Sanatel

AS139408 · SANATEL

PT Sanatel

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

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

This network elsewhere: the registry history of AS139361-AS139460, the block AS139408 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in Sanatel's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Sanatel'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 (3)

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. Singapore DE-CIX ASEAN Singapore, Singapore · PeeringDB 3472
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:df6:480:0:2:2090:0:1
    • In the entry with IPv4 103.162.254.148: set IPv6 to 2001:df6:480:0:2:2090:0:1 (now empty).
  2. Indonesia DE-CIX Jakarta Jakarta, Indonesia · PeeringDB 4411
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:df5:7880:0:2:2090:0:1
    • In the entry with IPv4 49.213.56.195: set IPv6 to 2001:df5:7880:0:2:2090:0:1 (now empty).
  3. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:2:5::6c
    • In the entry with IPv4 123.108.8.108: set IPv6 to 2001:7fa:2:5::6c (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

01234Oct 3, 2026Nov 19, 20264
Show as a table
DateExchanges
Nov 19, 20264
Nov 18, 20264
Nov 17, 20264
Nov 16, 20264
Nov 15, 20264
Nov 14, 20264
Nov 13, 20264
Nov 12, 20264
Nov 11, 20264
Nov 10, 20264
Nov 9, 20264
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, 20264
Oct 24, 20264
Oct 23, 20264
Oct 22, 20264
Oct 21, 20264
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

Map

Where Sanatel'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 22G across 4 exchanges.

Singapore DE-CIX ASEAN Singapore, Singapore 103.162.254.148 10G 2 routes Both IPv6 not in PeeringDB
Indonesia DE-CIX Jakarta Jakarta, Indonesia 49.213.56.195 10G 2 routes Both IPv6 not in PeeringDB
Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.8.108 1G Yes Both IPv6 not in PeeringDB
Indonesia JKT-IX Jakarta, Indonesia 119.11.185.155 1G Yes Both

Sanatel lists no facilities in PeeringDB.