asn.dev

Observed topology

AS219070 gbevm Eximia Networks Limited

Unclassified RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS219070: 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
AS52025ParadoxNetworks LimitedUnclassifiedIPv6117
AS6939Hurricane Electric LLCTransitIPv656
AS835GoCodeIT IncUnclassifiedIPv636
AS34927iFog GmbHHostingIPv633
AS39801France IX Services SASUUnclassifiedIPv617
AS35661VIRTUA SYSTEMS SASUnclassifiedIPv615
AS24482SG.GSHostingIPv62
AS48185team.blue NVUnclassifiedIPv62
AS50300CustodianDC LimitedUnclassifiedIPv62
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv62

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS219018Droidhub LTDUnclassifiedIPv633
AS399670HKSOFTUnclassifiedIPv633

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS52025ParadoxNetworks LimitedUnclassifiedIPv6182
AS6939Hurricane Electric LLCTransitIPv656
AS835GoCodeIT IncUnclassifiedIPv636
AS34927iFog GmbHHostingIPv633
AS219018Droidhub LTDUnclassifiedIPv633
AS399670HKSOFTUnclassifiedIPv633
AS39801France IX Services SASUUnclassifiedIPv617
AS35661VIRTUA SYSTEMS SASUnclassifiedIPv615
AS24482SG.GSHostingIPv62
AS48185team.blue NVUnclassifiedIPv62

All 17 adjacent →

Provenance

Where this comes from

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