asn.dev

Observed topology

AS18200 OPT-NC-AS-AP Office des Postes et Telecommunications New-Caledonia

Upstreams 5 carry this network
Downstreams 14 this network carries
Adjacent (IPv4) 20
Adjacent (IPv6) 17

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18200: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6764
AS6939Hurricane Electric LLCTransitIPv4 IPv6198
AS38195SuperloopUnclassifiedIPv4 IPv6170
AS24482SG.GSHostingIPv4 IPv621
AS64073Vetta GroupUnclassifiedIPv4 IPv621

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you.

Transit

Downstream networks

inferred

Networks for which AS18200 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS17480CANLResidentialIPv4 IPv6522
AS56089OFFRATELUnclassifiedIPv4 IPv6462
AS45345NautileResidentialIPv4 IPv6375
AS56055Micro Logic SystemsUnclassifiedIPv4 IPv6339
AS134405Data Services PacificUnclassifiedIPv4 IPv6284
AS2198RenaterUnclassifiedIPv4244
AS136402Nautile SARLUnclassifiedIPv4 IPv6215
AS45461TeleNetUnclassifiedIPv4 IPv6156
AS131248GOTVUnclassifiedIPv4 IPv695
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv695
AS141197Pacific CommunityUnclassifiedIPv4 IPv695
AS140718ENGIE PACIFIQUE INFORMATIQUEUnclassifiedIPv4 IPv694
AS137243INGENIERIE DES SYSTEMES DES INFORMATIONSUnclassifiedIPv461
AS20144ICANNUnclassifiedIPv4 IPv64

Adjacency

Adjacent networks

37 shown

Every AS seen directly next to AS18200 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv62,517
AS38195SuperloopUnclassifiedIPv4 IPv6896
AS6939Hurricane Electric LLCTransitIPv4 IPv6759
AS17480CANLResidentialIPv4 IPv6522
AS56089OFFRATELUnclassifiedIPv4 IPv6462
AS56055Micro Logic SystemsUnclassifiedIPv4 IPv6435
AS45345NautileResidentialIPv4 IPv6375
AS134405Data Services PacificUnclassifiedIPv4 IPv6284
AS2198RenaterUnclassifiedIPv4244
AS136402Nautile SARLUnclassifiedIPv4 IPv6215
AS45461TeleNetUnclassifiedIPv4 IPv6156
AS141197Pacific CommunityUnclassifiedIPv4 IPv695
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv695
AS131248GOTVUnclassifiedIPv4 IPv695
AS140718ENGIE PACIFIQUE INFORMATIQUEUnclassifiedIPv4 IPv694
AS24482SG.GSHostingIPv4 IPv667
AS64073Vetta GroupUnclassifiedIPv4 IPv667
AS137243INGENIERIE DES SYSTEMES DES INFORMATIONSUnclassifiedIPv461
AS24115EquinixHostingIPv45
AS20144ICANNUnclassifiedIPv4 IPv64

Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS18200, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 2 exchanges across 1 country and 1 region.

ExchangeLocationTheir addressMember ports
Megaport IX SydneySydney, Australia103.26.68.35271
Equinix Internet Exchange SydneySydney, Australia45.127.172.6238

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.03M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.