asn.dev

Observed topology

AS218914 DATAGIONET-AS - Datagio Systems Ltd.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS218914: 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
AS207208MEVSPACE sp. z o.o.UnclassifiedIPv4 IPv6233
AS219498Artem KovalchukUnclassifiedIPv4 IPv6185
AS214790Brainoza OUHostingIPv4 IPv692
AS16276OVH SASHostingIPv461
AS202413Pronkin TimofeiUnclassifiedIPv460
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198550NODE HOST LIMITEDUnclassifiedIPv4443
AS219498Artem KovalchukUnclassifiedIPv460
AS199479Amtp LLCUnclassifiedIPv42
AS214745Arseniy LikhacevUnclassifiedIPv61
AS218609Mukhammed MamedovUnclassifiedIPv61
AS219431Artur DibrovaUnclassifiedIPv61

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS207208MEVSPACE sp. z o.o.UnclassifiedIPv4 IPv6736
AS198550NODE HOST LIMITEDUnclassifiedIPv4443
AS219498Artem KovalchukUnclassifiedIPv4 IPv6245
AS214790Brainoza OUHostingIPv4 IPv692
AS16276OVH SASHostingIPv461
AS202413Pronkin TimofeiUnclassifiedIPv460
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv68
AS199479Amtp LLCUnclassifiedIPv42
AS214745Arseniy LikhacevUnclassifiedIPv61
AS218609Mukhammed MamedovUnclassifiedIPv61

All 11 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-18 10: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.