ixreport

WowNET

AS138074 · WowNET

PT. Wowrack Cepat Teknologi Nusantara

5Exchanges
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
1To fix in PeeringDB
4Facilities in PeeringDB

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

This network elsewhere: the registry history of AS138045-AS138144, the block AS138074 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in WowNET's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on WowNET'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 JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2404:c8:0:a:0:13:8074:1 2404:c8:0:a:0:13:8074:22404:c8:0:a:0:13:8074:1
    Port speed differs2 × 10G10G + 1G
    • In the entry with IPv4 119.11.185.107: set IPv6 to (empty) (now 2404:c8:0:a:0:13:8074:2); set Speed to 1000 (1G) (now 10000).

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 WowNET'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 33G across 5 exchanges.

Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.9.183 2001:7fa:2:5::1b7 1G Yes Both
Indonesia IIX-JawaTimur Surabaya, Indonesia 103.19.76.78 2001:7fa:2:50ba::1:2c 1G Yes PeeringDB
Indonesia JKT-IX Jakarta, Indonesia 119.11.184.66
119.11.185.107
2404:c8:0:a:0:13:8074:1
2404:c8:0:a:0:13:8074:2
2 × 10G Yes Both IPv6 not in exportSpeed differs
Indonesia JKT-IX Surabaya Surabaya, Indonesia 119.11.193.107 2404:c8:0:c:0:13:8074:1 10G Yes PeeringDB
Indonesia ODIX Omadata Surabaya, Indonesia 103.28.80.35 2403:1a00:55:659:a:13:8074:1 1G Yes PeeringDB

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

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

Indonesia NTT Jakarta 2 Data Center (JKT2)Jakarta 2 of 12
Indonesia OMADATA - E1 - SUBSurabaya 3 of 7
Indonesia neuCentrIX - Denpasar KaliasemDenpasar 0 of 2
Indonesia neuCentrIX - Surabaya GubengSurabaya 0 of 2