asn.dev

Observed topology

AS28133 Provedor Eloinet Ltda

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28133: 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
AS267549NetCOMM FIBRAUnclassifiedIPv4406
AS6939Hurricane Electric LLCTransitIPv4 IPv6373
AS23106AMERICAN TOWER DO BRASIL-COMUNICACAO MULTIMIDIA LTUnclassifiedIPv4 IPv6307
AS24482SG.GSHostingIPv4 IPv636
AS35280F5 Networks SARLHostingIPv422
AS37721Virtual Technologies & SolutionsResidentialIPv422

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS273590PVN Provedor De Internet LTDAUnclassifiedIPv4 IPv6125

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS23106AMERICAN TOWER DO BRASIL-COMUNICACAO MULTIMIDIA LTUnclassifiedIPv4 IPv6432
AS267549NetCOMM FIBRAUnclassifiedIPv4406
AS6939Hurricane Electric LLCTransitIPv4 IPv6373
AS273590PVN Provedor De Internet LTDAUnclassifiedIPv4 IPv6125
AS24482SG.GSHostingIPv4 IPv636
AS35280F5 Networks SARLHostingIPv422
AS37721Virtual Technologies & SolutionsResidentialIPv422

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-19 10: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.