asn.dev

Observed topology

AS3326 DATAGROUP Datagroup PJSC

Residential RIPE Cable/DSL/ISP

Upstreams 28 carry this network
Downstreams 233 this network carries
Adjacent (IPv4) 269
Adjacent (IPv6) 53
Upstream graph Who carries AS3326, and who carries them, drawn as a map up to the transit-free core. 7 exchanges Where AS3326 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 28

Networks observed carrying traffic for AS3326: 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
AS1299Arelion Sweden ABTransitIPv4 IPv61,817
AS9002RETN LimitedUnclassifiedIPv4 IPv6919
AS6939Hurricane Electric LLCTransitIPv4 IPv6847
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6361
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv6106
AS24482SG.GSHostingIPv4 IPv6106
AS48185team.blue NVUnclassifiedIPv4 IPv6106
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv6106
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv6106
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv6106

All 28 upstreams →

Transit

Downstream networks

All 233

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

ASNetworkTypeFamiliesPaths seen
AS31520PRIVATE JOINT STOCK COMPANY "DATAGROUP"UnclassifiedIPv413,570
AS25229Limited Liability Company "KYIVSKI TELEKOMUNIKATSIYNI MEREZHI"UnclassifiedIPv46,076
AS34058Limited Liability Company "lifecell"UnclassifiedIPv4 IPv61,543
AS15785PRIVATE JOINT STOCK COMPANY "DATAGROUP"UnclassifiedIPv4 IPv61,399
AS7155ViaSat,Inc.ResidentialIPv41,003
AS35680Volia-Cable LLCUnclassifiedIPv41,003
AS42655ON-LINE LtdUnclassifiedIPv4713
AS21500Scientific Production Enterprise "Technaukservice" LtdResidentialIPv4632
AS43067PE "Pretcher"UnclassifiedIPv4 IPv6629
AS3236SERVER.UA LLCHostingIPv4 IPv6566

All 233 downstreams →

Adjacency

Adjacent networks

All 273

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv615,107
AS31520PRIVATE JOINT STOCK COMPANY "DATAGROUP"UnclassifiedIPv413,570
AS9002RETN LimitedUnclassifiedIPv4 IPv68,238
AS25229Limited Liability Company "KYIVSKI TELEKOMUNIKATSIYNI MEREZHI"UnclassifiedIPv46,161
AS174Cogent Communications, LLCTransitIPv4 IPv65,672
AS6939Hurricane Electric LLCTransitIPv4 IPv65,327
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv63,286
AS21219PRIVATE JOINT STOCK COMPANY "DATAGROUP"ResidentialIPv42,475
AS34058Limited Liability Company "lifecell"UnclassifiedIPv4 IPv61,543
AS15785PRIVATE JOINT STOCK COMPANY "DATAGROUP"UnclassifiedIPv4 IPv61,399

All 273 adjacent →

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.