ixreport

CYBEREVO

AS152787 · CYBEREVO

Jaringan Cyber Evo

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

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

This network elsewhere: the registry history of AS152743-AS152842, the block AS152787 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on CYBEREVO'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 (4)

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:54d3:0:1
    Port speed differs500M10G
    • In the entry with IPv4 103.162.254.145: set IPv6 to 2001:df6:480:0:2:54d3:0:1 (now empty); set Speed to 10000 (10G) (now 500).
  2. Indonesia DE-CIX Jakarta Jakarta, Indonesia · PeeringDB 4411
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:df5:7880:0:2:54d3:0:2
    • In the entry with IPv4 49.213.56.74: set IPv6 to 2001:df5:7880:0:2:54d3:0:2 (now empty).
  3. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:2:5::34b
    Port speed differs10G1G
    • In the entry with IPv4 123.108.11.59: set IPv6 to 2001:7fa:2:5::34b (now empty); 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.

  4. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2404:c8:0:a:0:15:2787:1
    Port speed differs40G100G
    • In the entry with IPv4 119.11.186.206: set IPv6 to 2404:c8:0:a:0:15:2787:1 (now empty); set Speed to 100000 (100G) (now 40000).

Exchanges over time

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

Map

Where CYBEREVO'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 80.5G across 6 exchanges.

Indonesia AIX Tapos, Depok, Indonesia 43.254.82.152 10G Yes Both
Singapore DE-CIX ASEAN Singapore, Singapore 103.162.254.145 500M 3 routes Both IPv6 not in PeeringDBSpeed differs
Indonesia DE-CIX Jakarta Jakarta, Indonesia 49.213.56.74 10G 3 routes Both IPv6 not in PeeringDB
Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.11.59 10G Yes Both IPv6 not in PeeringDBSpeed differs
Indonesia JKT-IX Jakarta, Indonesia 119.11.186.206 40G Yes Both IPv6 not in PeeringDBSpeed differs
Indonesia OMNIIX INDONESIA Batam, Jakarta, Indonesia 43.255.59.90 10G Both

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

These exchanges have a switch in a facility where CYBEREVO lists itself in PeeringDB, but don't have CYBEREVO 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; IDC 3D
Indonesia BIX JakartaJakarta, Indonesia 180 Datacenter APJII-Cyber; IDC 3D
Indonesia ILIXSurabaya, Indonesia 122 Datacenter APJII-Cyber
Indonesia Transhybrid IX NetworkJakarta, Indonesia 63 Datacenter APJII-Cyber; IDC 3D
Indonesia CENTRO-IXPekanbaru - Jakarta, Indonesia 39 Datacenter APJII-Cyber
Indonesia CNI-IXJakarta, Indonesia 18 Datacenter APJII-Cyber; IDC 3D
Indonesia Metta-IXJakarta, Indonesia 16 Datacenter APJII-Cyber
Indonesia GPMIXLampung Timur, Indonesia 13 Datacenter APJII-Cyber
Indonesia JDXJakarta, Indonesia 13 Datacenter APJII-Cyber; IDC 3D
Indonesia Swin ExchangeDepok, Indonesia 13 IDC 3D
Indonesia BatamIX JakartaJakarta, Indonesia 7 Datacenter APJII-Cyber; IDC 3D
Indonesia IFORTE XchangeJakarta, Indonesia 7 IDC 3D
Indonesia Super Internet eXchange (SIX)Bogor, Indonesia 4 Datacenter APJII-Cyber
Indonesia ABS-IXJAKARTA, Indonesia 3 Datacenter APJII-Cyber
Facilities (2)

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

Indonesia Datacenter APJII-CyberJakarta Selatan 4 of 17
Indonesia IDC 3DJakarta Selatan 4 of 12

Recent changes Search them

  • Oct 14, 2026 [PDB] AS152787 CYBEREVO now in PeeringDB at OMNIIX INDONESIA
  • Oct 7, 2026 [WEB] AS152787 CYBEREVO added to OMNIIX INDONESIA