ixreport

Nebula Global: PeeringDB fix list

AS140224 · peeringdb.com/net/32294

PeeringDB

3 things to fix in Nebula Global's PeeringDB record, from what its exchanges publish: 3 to check. As of 2026-10-08 18:53 UTC.

Make the changes on Nebula Global's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Check these entries (3)

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

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126Not on its website members list
    IPv4101.203.90.57
    IPv62001:de8:c::14:224:1
    Speed100000 Mbps (100G)

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

  2. Hong Kong HKIX Hong Kong, Hong Kong · PeeringDB 42Not on its IX-F export
    IPv4123.255.90.173
    IPv62001:7fa:0:1::ca28:a0ad
    Speed100000 Mbps (100G)
  3. Singapore SGIX Singapore, Singapore · PeeringDB 429Not on its IX-F export or website members list
    IPv4103.16.103.9
    IPv62001:de8:12:100::103:9
    Speed100000 Mbps (100G)

From ixreport.com/net/140224/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.