asn.dev

Observed topology

AS35026 GELICON-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35026: 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
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv6166
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv622
AS24482SG.GSHostingIPv45
AS37721Virtual Technologies & SolutionsResidentialIPv45
AS8732JSC ComcorUnclassifiedIPv43
AS25091IP-Max SAUnclassifiedIPv43
AS34927iFog GmbHHostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198675Gelicon-Apple Limited liability companyUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv6166
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv622
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS24482SG.GSHostingIPv45
AS8732JSC ComcorUnclassifiedIPv43
AS25091IP-Max SAUnclassifiedIPv43
AS34927iFog GmbHHostingIPv43
AS198675Gelicon-Apple Limited liability companyUnclassifiedIPv41

Provenance

Where this comes from

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