ixreport

Komorebi

AS199762 · Komorebi

Adita Tarkono Putra

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

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

This network elsewhere: its registry history on RIR Tracker

PeeringDB fix list Printable page · CSV

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

Make the changes on Komorebi'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 (2)

On the exchange's own member list, but not in Komorebi's PeeringDB record. Add one entry per connection with these values.

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4185.1.125.44
    IPv62001:7f8:d0::3:c52:1
    SpeedNot published
    RS peerYes
  2. Canada UNM-Exch Canada-West Vancouver, Canada · PeeringDB 2452From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4192.34.27.118
    IPv6–
    SpeedNot published
    RS peerNot published
    IPv4–
    IPv62602:ffb1:200:0:192:34:27:118
    SpeedNot published
    RS peerNot published

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

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

Check these entries (1)

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

  1. Indonesia CXC Jakarta Jakarta, Indonesia · PeeringDB 2737Not on its website members list
    IPv4–
    IPv62400:9c80:0:173::199:762
    Speed1000 Mbps (1G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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 Komorebi'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 11G, at the 2 of 4 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 185.1.125.44 2001:7f8:d0::3:c52:1 Yes Not in PeeringDB
Indonesia CXC Jakarta Jakarta, Indonesia 2400:9c80:0:173::199:762 1G Yes PeeringDB only
Indonesia JKT-IX Jakarta, Indonesia 119.11.186.17 2404:c8:0:a:0:19:9762:1 10G Yes Both Speed differs
Canada UNM-Exch Canada-West Vancouver, Canada 192.34.27.118 2602:ffb1:200:0:192:34:27:118 Not in PeeringDB

Komorebi lists no facilities in PeeringDB.