asn.dev

Observed topology

AS273744 MOG LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS273744: 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
AS265269TELE INFORMATICAUnclassifiedIPv4 IPv6137
AS6939Hurricane Electric LLCTransitIPv4 IPv672
AS262503TELECOMUNICACOES EIRELIUnclassifiedIPv459
AS24482SG.GSHostingIPv4 IPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263304NET LTDAUnclassifiedIPv4177
AS270256TELECOMUnclassifiedIPv4177
AS266353BJNET TELECOMUNICACOES LTDA-MEResidentialIPv458
AS271493NET PEDRAUnclassifiedIPv457
AS273764TELECOM LTDAUnclassifiedIPv631
AS274814C. ARAUJOUnclassifiedIPv631

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS265269TELE INFORMATICAUnclassifiedIPv4 IPv6545
AS270256TELECOMUnclassifiedIPv4185
AS263304NET LTDAUnclassifiedIPv4177
AS6939Hurricane Electric LLCTransitIPv4 IPv6148
AS262503TELECOMUNICACOES EIRELIUnclassifiedIPv4107
AS266353BJNET TELECOMUNICACOES LTDA-MEResidentialIPv458
AS271493NET PEDRAUnclassifiedIPv457
AS273764TELECOM LTDAUnclassifiedIPv631
AS274814C. ARAUJOUnclassifiedIPv631
AS24482SG.GSHostingIPv4 IPv613

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.