asn.dev

Observed topology

AS268214 schossler e silva ltda - me

Residential AFRINIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268214: 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
AS273461CYBERWEB ATJP LTDAUnclassifiedIPv4 IPv696
AS6939Hurricane Electric LLCTransitIPv4 IPv635
AS24482SG.GSHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264141Vale do Ribeira Internet Ltda - MeUnclassifiedIPv461
AS270998Gehling & Mulling LtdaUnclassifiedIPv649
AS273461CYBERWEB ATJP LTDAUnclassifiedIPv639
AS274626Lm Telecom LTDAUnclassifiedIPv62
AS267501Equatorial Telecomunicacoes LTDAResidentialIPv61

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS273461CYBERWEB ATJP LTDAUnclassifiedIPv4 IPv6208
AS6939Hurricane Electric LLCTransitIPv4 IPv6101
AS264141Vale do Ribeira Internet Ltda - MeUnclassifiedIPv461
AS270998Gehling & Mulling LtdaUnclassifiedIPv649
AS24482SG.GSHostingIPv610
AS35280F5 Networks SARLHostingIPv62
AS37721Virtual Technologies & SolutionsResidentialIPv62
AS274626Lm Telecom LTDAUnclassifiedIPv62
AS267501Equatorial Telecomunicacoes LTDAResidentialIPv61

Provenance

Where this comes from

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