asn.dev

Observed topology

AS41268 SESAMEWARE-AS Sesameware FZ-LLC

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS41268: 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
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv615
AS8359MTS PJSCMobileIPv64
AS31500Global Network Management IncUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS61436INTEX ltd.UnclassifiedIPv4 IPv6179
AS57629LLC IVI.RUHostingIPv635

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS61436INTEX ltd.UnclassifiedIPv4 IPv6179
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6118
AS31133PJSC MegaFonMobileIPv4 IPv654
AS57629LLC IVI.RUHostingIPv635
AS8359MTS PJSCMobileIPv4 IPv626
AS3216PJSC "Vimpelcom"MobileIPv4 IPv625
AS12389PJSC RostelecomResidentialIPv68
AS24482SG.GSHostingIPv62
AS31500Global Network Management IncUnclassifiedIPv41

Provenance

Where this comes from

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