asn.dev

Observed topology

AS16128 AGARIK-NETWORK AGARIK provide WEB, Servers Hosting and dedicated Internet Connection

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS16128: 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
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6332
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv663
AS6939Hurricane Electric LLCTransitIPv4 IPv637
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv64
AS6696VERIXI SAUnclassifiedIPv43
AS20766Association "Gitoyen"UnclassifiedIPv43
AS34927iFog GmbHHostingIPv43
AS37100SEACOM LimitedUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS6ATOS IT Solutions and Services, Inc.UnclassifiedIPv4360

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6482
AS6ATOS IT Solutions and Services, Inc.UnclassifiedIPv4360
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6183
AS6939Hurricane Electric LLCTransitIPv4 IPv685
AS24482SG.GSHostingIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv610
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv610
AS6696VERIXI SAUnclassifiedIPv49
AS20766Association "Gitoyen"UnclassifiedIPv49
AS34927iFog GmbHHostingIPv49

Provenance

Where this comes from

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