asn.dev

Observed topology

AS205275 ROMARG ROMARG SRL

Unclassified RIPE

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

Transit

Upstream networks

All 31

Networks observed carrying traffic for AS205275: 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 ABTransitIPv4558
AS3356Level 3 Parent, LLCTransitIPv4454
AS6939Hurricane Electric LLCTransitIPv4372
AS5405Inter.link GmbHUnclassifiedIPv4310
AS57463NetIX Communications JSCUnclassifiedIPv4248
AS34549meerfarbig GmbH & Co. KGHostingIPv4124
AS50304Blix Solutions ASUnclassifiedIPv4124
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4119
AS12302Vodafone Romania S.A.ResidentialIPv4114
AS293ESnetUnclassifiedIPv462

All 31 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 31

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4558
AS3356Level 3 Parent, LLCTransitIPv4454
AS6939Hurricane Electric LLCTransitIPv4372
AS5405Inter.link GmbHUnclassifiedIPv4310
AS57463NetIX Communications JSCUnclassifiedIPv4248
AS34549meerfarbig GmbH & Co. KGHostingIPv4124
AS50304Blix Solutions ASUnclassifiedIPv4124
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4119
AS12302Vodafone Romania S.A.ResidentialIPv4114
AS293ESnetUnclassifiedIPv462

All 31 adjacent →

Provenance

Where this comes from

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