asn.dev

Observed topology

AS61094 CRATIS-AS CRATIS Ltd.

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61094: 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
AS1299Arelion Sweden ABTransitIPv4232
AS3223Voxility LLPHostingIPv4174
AS9002RETN LimitedUnclassifiedIPv4168
AS174Cogent Communications, LLCTransitIPv495
AS6939Hurricane Electric LLCTransitIPv486
AS44306OMONIA d.o.o.UnclassifiedIPv430
AS5391Hrvatski Telekom d.d.ResidentialIPv420

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS41454Optika Kabel TV d.o.o.UnclassifiedIPv4243
AS212550Sedmi Odjel d.o.o.UnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS41454Optika Kabel TV d.o.o.UnclassifiedIPv4311
AS44306OMONIA d.o.o.UnclassifiedIPv4277
AS1299Arelion Sweden ABTransitIPv4232
AS3223Voxility LLPHostingIPv4174
AS9002RETN LimitedUnclassifiedIPv4168
AS5391Hrvatski Telekom d.d.ResidentialIPv4136
AS174Cogent Communications, LLCTransitIPv495
AS6939Hurricane Electric LLCTransitIPv494
AS212550Sedmi Odjel d.o.o.UnclassifiedIPv460

Provenance

Where this comes from

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