asn.dev

Observed topology

AS55803 HOSTOPIA-AU Hostopia Australia Web Pty Ltd

Upstreams 8 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 8

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55803: 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
AS38195SuperloopUnclassifiedIPv4 IPv6806
AS2914NTT America, Inc.TransitIPv4 IPv6704
AS174Cogent Communications, LLCTransitIPv4 IPv6697
AS6939Hurricane Electric LLCTransitIPv679
AS60068Datacamp LimitedHostingIPv453
AS24482SG.GSHostingIPv4 IPv641
AS64073Vetta GroupUnclassifiedIPv4 IPv632
AS24115EquinixHostingIPv413

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 AS55803 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS38719Dreamscape Networks LimitedHostingIPv4 IPv62,470
AS1921ipcom GmbHHostingIPv4 IPv625

Adjacency

Adjacent networks

18 shown

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

ASNetworkTypeFamiliesPaths seen
AS38719Dreamscape Networks LimitedHostingIPv4 IPv62,470
AS174Cogent Communications, LLCTransitIPv4 IPv61,727
AS2914NTT America, Inc.TransitIPv4 IPv61,673
AS38195SuperloopUnclassifiedIPv4 IPv61,076
AS6939Hurricane Electric LLCTransitIPv6282
AS60068Datacamp LimitedHostingIPv453
AS64073Vetta GroupUnclassifiedIPv4 IPv651
AS24482SG.GSHostingIPv4 IPv642
AS1921ipcom GmbHHostingIPv4 IPv625
AS24115EquinixHostingIPv415
AS7575Australian Academic and Research Network (AARNet)EducationIPv41

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 AS55803, 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 6 exchanges across 1 country and 1 region.

ExchangeLocationTheir addressMember ports
Megaport IX SydneySydney, Australia103.26.68.27271
Equinix Internet Exchange SydneySydney, Australia45.127.172.136238
IX Australia (Sydney NSW)Sydney, Australia218.100.52.92199
Megaport IX MelbourneMelbourne, Australia103.26.71.25152
IX Australia (Melbourne VIC)Melbourne, Australia218.100.78.142108
Equinix Internet Exchange MelbourneMelbourne, Australia183.177.61.4659

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-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M 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-08 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,137 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.