asn.dev

Observed topology

AS53019 infotec- servicos de provedor da internet ltda

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS53019: 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
AS53087Ltda.ResidentialIPv4 IPv6911
AS267613S.A.UnclassifiedIPv4 IPv6196
AS6939Hurricane Electric LLCTransitIPv682

Transit

Downstream networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS269040MEUnclassifiedIPv4300
AS263960telecomUnclassifiedIPv4 IPv6248
AS272641Internet e TecnologiaUnclassifiedIPv6195
AS263995BRASIL LTDAUnclassifiedIPv4 IPv6186
AS263926MEUnclassifiedIPv4 IPv6158
AS268314DA SILVA LOPES TELECOMUNICACOESUnclassifiedIPv4 IPv6153
AS266935INFORMATICA EIRELIUnclassifiedIPv4119
AS271132INTERNETUnclassifiedIPv4 IPv693
AS267315NET PROVEDOR DE INTERNET LTDAUnclassifiedIPv4 IPv663
AS265896TelecomunicacoesUnclassifiedIPv460

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS53087Ltda.ResidentialIPv4 IPv61,772
AS267613S.A.UnclassifiedIPv4 IPv6824
AS269040MEUnclassifiedIPv4300
AS6939Hurricane Electric LLCTransitIPv6297
AS263960telecomUnclassifiedIPv4 IPv6248
AS272641Internet e TecnologiaUnclassifiedIPv6195
AS263995BRASIL LTDAUnclassifiedIPv4 IPv6186
AS263926MEUnclassifiedIPv4 IPv6158
AS268314DA SILVA LOPES TELECOMUNICACOESUnclassifiedIPv4 IPv6153
AS266935INFORMATICA EIRELIUnclassifiedIPv4125

Provenance

Where this comes from

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