asn.dev

Observed topology

AS47600 RUBIXDATACENTER

Hosting RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS47600: 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
AS174Cogent Communications, LLCTransitIPv4378
AS6939Hurricane Electric LLCTransitIPv4 IPv697
AS39801France IX Services SASUUnclassifiedIPv418
AS24482SG.GSHostingIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv610
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv610
AS12779IT.Gate S.p.A.UnclassifiedIPv49
AS20766Association "Gitoyen"UnclassifiedIPv49
AS33891Core-Backbone GmbHHostingIPv49
AS34927iFog GmbHHostingIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS212298SASU OXIWIUnclassifiedIPv4120
AS20148Vantiva USA Shared Services Inc.UnclassifiedIPv461
AS201636Tec6 SASUnclassifiedIPv460

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4545
AS6939Hurricane Electric LLCTransitIPv4 IPv6134
AS212298SASU OXIWIUnclassifiedIPv4120
AS20148Vantiva USA Shared Services Inc.UnclassifiedIPv461
AS201636Tec6 SASUnclassifiedIPv460
AS39801France IX Services SASUUnclassifiedIPv426
AS24482SG.GSHostingIPv4 IPv614
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv614
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv614
AS12779IT.Gate S.p.A.UnclassifiedIPv413

Provenance

Where this comes from

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