Nebula Global LLC: PeeringDB fix list
AS18186 · peeringdb.com/net/37760
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-10-08 18:53 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.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 103.16.103.9 IPv6 2001:de8:12:100::103:9 Speed 100000 Mbps (100G) RS peer Yes
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.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 103.16.103.9 is AS140224 Nebula Global 103.16.103.9 Address belongs to another network in PeeringDB 2001:de8:12:100::103:9 is AS140224 Nebula Global 2001: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.
From ixreport.com/net/18186/: 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.