asn.dev

Observed topology

AS47608 GIGALIS-AS GROUPEMENT D'INTERET PUBLIC GIGALIS

Unclassified RIPE NSP

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS47608: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv693
AS174Cogent Communications, LLCTransitIPv4 IPv651
AS6939Hurricane Electric LLCTransitIPv4 IPv634
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv64
AS6696VERIXI SAUnclassifiedIPv43
AS9002RETN LimitedUnclassifiedIPv63
AS12779IT.Gate S.p.A.UnclassifiedIPv43
AS20562Broadband Hosting B.V.HostingIPv43

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS43249LUMINESS SASUnclassifiedIPv4106
AS200906MCT SASUnclassifiedIPv418

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6165
AS43249LUMINESS SASUnclassifiedIPv4106
AS174Cogent Communications, LLCTransitIPv4 IPv675
AS6939Hurricane Electric LLCTransitIPv4 IPv648
AS200906MCT SASUnclassifiedIPv418
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv66
AS12779IT.Gate S.p.A.UnclassifiedIPv45
AS33891Core-Backbone GmbHHostingIPv45

All 18 adjacent →

Provenance

Where this comes from

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