ixreport

Nebula Global LLC

AS18186

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

Tools: Where can I peer with Nebula Global LLC? · Where should Nebula Global LLC peer next? · Compare Nebula Global LLC with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

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

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

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  2. Hong Kong HKIX Hong Kong, Hong Kong · PeeringDB 42From its IX-F export and website members list

    The exchange's IX-F export and website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  3. Singapore SGIX Singapore, Singapore · PeeringDB 429From its IX-F export and website members list
    IPv4103.16.103.9
    IPv62001:de8:12:100::103:9
    Speed100000 Mbps (100G)
    RS peerYes

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. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB103.16.103.9 is AS140224 Nebula Global103.16.103.9
    Address belongs to another network in PeeringDB2001:de8:12:100::103:9 is AS140224 Nebula Global2001:de8:12:100::103:9

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

Exchanges over time

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

Map

Where Nebula Global LLC'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 100G, at the 1 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Japan BBIX Tokyo Tokyo, Japan Not in PeeringDB
Hong Kong HKIX Hong Kong, Hong Kong Not in PeeringDB
Singapore SGIX Singapore, Singapore 103.16.103.9 2001:de8:12:100::103:9 100G Yes Not in PeeringDB Address taken

Nebula Global LLC lists no facilities in PeeringDB.