asn.dev

Observed topology

AS266448 GIGA MAIS FIBRA TELECOMUNICACOES S.A.

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266448: 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
AS268424GIGA MAIS FIBRA TELECOMUNICACOES S.A.UnclassifiedIPv4 IPv683
AS13786Seabras 1 USA, LLCUnclassifiedIPv633
AS6939Hurricane Electric LLCTransitIPv49
AS24482SG.GSHostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264524GIGA MAIS FIBRA TELECOMUNICACOES S.A.UnclassifiedIPv4 IPv6132
AS271018Universal Net - Servicos de Comunicacao Mult LTDAUnclassifiedIPv412

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS264524GIGA MAIS FIBRA TELECOMUNICACOES S.A.UnclassifiedIPv4 IPv6204
AS268424GIGA MAIS FIBRA TELECOMUNICACOES S.A.UnclassifiedIPv4 IPv6142
AS13786Seabras 1 USA, LLCUnclassifiedIPv4 IPv691
AS6939Hurricane Electric LLCTransitIPv457
AS24482SG.GSHostingIPv4 IPv613
AS271018Universal Net - Servicos de Comunicacao Mult LTDAUnclassifiedIPv412
AS35280F5 Networks SARLHostingIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48

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.