asn.dev

Observed topology

AS263997 BITMAIL SERVICOS DE INFORMATICA LTDA - ME

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263997: 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 IPv6230
AS6939Hurricane Electric LLCTransitIPv660
AS265269MEGA TELE INFORMATICAUnclassifiedIPv455
AS268024TURBONET CAXIASUnclassifiedIPv4 IPv610

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268037OK NET INFOR LTDAUnclassifiedIPv4 IPv694
AS268024TURBONET CAXIASUnclassifiedIPv493
AS273717TECNONET SINAL DE INTERNET LTDAUnclassifiedIPv4 IPv613

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS269194ST1 INTERNETResidentialIPv4 IPv6426
AS268024TURBONET CAXIASUnclassifiedIPv4 IPv6103
AS268037OK NET INFOR LTDAUnclassifiedIPv4 IPv694
AS6939Hurricane Electric LLCTransitIPv660
AS265269MEGA TELE INFORMATICAUnclassifiedIPv459
AS273717TECNONET SINAL DE INTERNET LTDAUnclassifiedIPv4 IPv613

Provenance

Where this comes from

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