asn.dev

Observed topology

AS271084 AS271084 - TRYMNET PROVEDOR

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS271084: 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
AS269194ST1 INTERNETResidentialIPv4 IPv6221
AS262456ELO MULTIMIDIA LTDAResidentialIPv461
AS265484CLICK ENTER LTDA - MEResidentialIPv620
AS6939Hurricane Electric LLCTransitIPv49
AS24482SG.GSHostingIPv4 IPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263975Smart Link Consultoria e servicos em telec. LTDAUnclassifiedIPv4 IPv697
AS263343PC2 TELECOMUnclassifiedIPv4 IPv696
AS28135ASSOCIACAO NACIONAL PARA INCLUSAO DIGITAL - ANIDUnclassifiedIPv461
AS270885VITORIA NETUnclassifiedIPv410

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS269194ST1 INTERNETResidentialIPv4 IPv6416
AS263975Smart Link Consultoria e servicos em telec. LTDAUnclassifiedIPv4 IPv697
AS263343PC2 TELECOMUnclassifiedIPv4 IPv696
AS28135ASSOCIACAO NACIONAL PARA INCLUSAO DIGITAL - ANIDUnclassifiedIPv461
AS262456ELO MULTIMIDIA LTDAResidentialIPv461
AS265484CLICK ENTER LTDA - MEResidentialIPv661
AS6939Hurricane Electric LLCTransitIPv433
AS270885VITORIA NETUnclassifiedIPv410
AS24482SG.GSHostingIPv4 IPv66

Provenance

Where this comes from

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