asn.dev

Observed topology

AS41765 IPGARDE-AS

Unclassified RIPE Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS41765: 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 IPv6254
AS3356Level 3 Parent, LLCTransitIPv4 IPv6187
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4122
AS174Cogent Communications, LLCTransitIPv4 IPv6118
AS30781Free Pro SASHostingIPv4 IPv666
AS204092Association GRIFONUnclassifiedIPv4 IPv613
AS6696VERIXI SAUnclassifiedIPv411
AS35661VIRTUA SYSTEMS SASUnclassifiedIPv62
AS34927iFog GmbHHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS200607Manifone SASUnclassifiedIPv4108
AS209053S.F.G S.A.UnclassifiedIPv460
AS49553AXE INFORMATIQUE SASUnclassifiedIPv459

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6332
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4234
AS3356Level 3 Parent, LLCTransitIPv4 IPv6187
AS174Cogent Communications, LLCTransitIPv4 IPv6144
AS200607Manifone SASUnclassifiedIPv4108
AS30781Free Pro SASHostingIPv4 IPv669
AS209053S.F.G S.A.UnclassifiedIPv460
AS49553AXE INFORMATIQUE SASUnclassifiedIPv459
AS204092Association GRIFONUnclassifiedIPv4 IPv619
AS6696VERIXI SAUnclassifiedIPv413

All 12 adjacent →

Provenance

Where this comes from

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