asn.dev

Observed topology

AS269228 NETWORK SERVIcOS DE INFORMATICA Ltda.

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269228: 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
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6189
AS13786Seabras 1 USA, LLCUnclassifiedIPv675
AS265061MIRIANE ARAUJO LIMA DE OLIVEIRA - MEUnclassifiedIPv4 IPv652
AS270389Horacio Machado de AquinoUnclassifiedIPv438
AS6939Hurricane Electric LLCTransitIPv617

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271643Flt Solutions TelecomUnclassifiedIPv448

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6237
AS13786Seabras 1 USA, LLCUnclassifiedIPv675
AS265061MIRIANE ARAUJO LIMA DE OLIVEIRA - MEUnclassifiedIPv4 IPv652
AS271643Flt Solutions TelecomUnclassifiedIPv448
AS270389Horacio Machado de AquinoUnclassifiedIPv438
AS6939Hurricane Electric LLCTransitIPv617

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.