asn.dev

Observed topology

AS140637 MTG-MG Macquarie Technology Operations Pty Limited

Unclassified APNIC NSP

Upstreams 6 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 4
Upstream graph Who carries AS140637, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS140637 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS140637: 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
AS17477Macquarie Technology Operations Pty LimitedResidentialIPv42,157
AS32787Akamai Technologies, Inc.HostingIPv4 IPv6564
AS198949Radware LtdUnclassifiedIPv4360
AS4826Vocus Connect International BackboneUnclassifiedIPv633
AS24482SG.GSHostingIPv4 IPv66
AS64073Vetta GroupUnclassifiedIPv4 IPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS136232Independent Commission Against CorruptionUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS17477Macquarie Technology Operations Pty LimitedResidentialIPv42,218
AS32787Akamai Technologies, Inc.HostingIPv4 IPv6564
AS198949Radware LtdUnclassifiedIPv4360
AS136232Independent Commission Against CorruptionUnclassifiedIPv461
AS4826Vocus Connect International BackboneUnclassifiedIPv633
AS24482SG.GSHostingIPv4 IPv66
AS64073Vetta GroupUnclassifiedIPv4 IPv66

Provenance

Where this comes from

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

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. 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.

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