asn.dev

Observed topology

AS275808 AS275808 - LMPBR18

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS275808: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6710
AS273421MAZA TelecomUnclassifiedIPv4 IPv659
AS263152MIGO TELECOMResidentialIPv624
AS24482SG.GSHostingIPv4 IPv621

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS273478Sage NetworksUnclassifiedIPv460
AS61932JCN COMUNICACOES E INFORMATICA LTDA MEUnclassifiedIPv449

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6762
AS273421MAZA TelecomUnclassifiedIPv4 IPv6110
AS273478Sage NetworksUnclassifiedIPv460
AS61932JCN COMUNICACOES E INFORMATICA LTDA MEUnclassifiedIPv449
AS263152MIGO TELECOMResidentialIPv4 IPv629
AS24482SG.GSHostingIPv4 IPv622

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.