asn.dev

Observed topology

AS268914 ERIQUELSON SILVA DE SOUTO - ME

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268914: 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
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv6210
AS263025ISPTEC Sistemas de Comunicacao EireliResidentialIPv4 IPv694
AS6939Hurricane Electric LLCTransitIPv4 IPv656
AS263022CARIRIWEB PROVEDORES DE INTERNET LTDAUnclassifiedIPv413

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270437LINK FLEX INTERNET EIRELIUnclassifiedIPv4 IPv6279
AS274630RMNET TELECOMUnclassifiedIPv633

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv6408
AS270437LINK FLEX INTERNET EIRELIUnclassifiedIPv4 IPv6279
AS6939Hurricane Electric LLCTransitIPv4 IPv6157
AS263025ISPTEC Sistemas de Comunicacao EireliResidentialIPv4 IPv694
AS274630RMNET TELECOMUnclassifiedIPv633
AS263022CARIRIWEB PROVEDORES DE INTERNET LTDAUnclassifiedIPv426

Provenance

Where this comes from

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