ixreport

Cloudland Limited CL3/SY01

AS136499

Cloudland Limited

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

Tools: Where can I peer with Cloudland Limited CL3/SY01? · Where should Cloudland Limited CL3/SY01 peer next? · Compare Cloudland Limited CL3/SY01 with another network

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

PeeringDB fix list Printable page · CSV

2 things to fix in Cloudland Limited CL3/SY01's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Cloudland Limited CL3/SY01'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 (2)

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. New Zealand MegaIX Auckland Auckland, New Zealand · PeeringDB 984
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:40::3a 2001:dea:0:40::54
    • In the entry with IPv4 43.243.22.58: set IPv6 to 2001:dea:0:40::3a (now empty).
    • In the entry with IPv4 43.243.22.84: set IPv6 to 2001:dea:0:40::54 (now empty).

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

  2. Australia MegaIX Sydney Sydney, Australia · PeeringDB 780
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:10::1f
    • In the entry with IPv4 103.26.68.31: set IPv6 to 2001:dea:0:10::1f (now empty).

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

Exchanges over time

012Oct 3, 2026Nov 19, 20262
Show as a table
DateExchanges
Nov 19, 20262
Nov 18, 20262
Nov 17, 20262
Nov 16, 20262
Nov 15, 20262
Nov 14, 20262
Nov 13, 20262
Nov 12, 20262
Nov 11, 20262
Nov 10, 20262
Nov 9, 20262
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, 20262
Oct 19, 20262
Oct 18, 20262
Oct 17, 20262
Oct 16, 20262
Oct 15, 20262
Oct 14, 20262
Oct 13, 20262
Oct 12, 20262
Oct 11, 20262
Oct 10, 20262
Oct 9, 20262
Oct 8, 20262
Oct 7, 20262
Oct 6, 20262
Oct 5, 20262
Oct 4, 20262
Oct 3, 20262

Map

Where Cloudland Limited CL3/SY01'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 30G across 2 exchanges.

New Zealand MegaIX Auckland Auckland, New Zealand 43.243.22.58
43.243.22.84
2 × 10G Yes Both IPv6 not in PeeringDB
Australia MegaIX Sydney Sydney, Australia 103.26.68.31 10G Yes Both IPv6 not in PeeringDB

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

These exchanges have a switch in a facility where Cloudland Limited CL3/SY01 lists itself in PeeringDB, but don't have Cloudland Limited CL3/SY01 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 (3)

The buildings Cloudland Limited CL3/SY01 lists in PeeringDB, and how many of the exchanges in each it's on.

New Zealand Data Vault Auckland Data CenterAuckland 1 of 4
New Zealand Datacom - Orbit Data Centre (Auckland)Auckland 1 of 3
Australia AirTrunk SYD1Huntingwood 1 of 1