asn.dev

Observed topology

AS205209 BYNET-BUSINESS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS205209: 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
AS25003Internet Binat LtdUnclassifiedIPv41,276

Transit

Downstream networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS28783Netafim LTDUnclassifiedIPv4180
AS48068VISONIC LIMITEDUnclassifiedIPv4180
AS49069AspireGlobal Marketing Solutions LtdUnclassifiedIPv461
AS206531B.D.I.-COFACE LTDUnclassifiedIPv461
AS47461Starhome Mach GmbHUnclassifiedIPv460
AS47766Haifa Port Company LtdUnclassifiedIPv460
AS50865AMIAD WATER SYSTEMS LTDUnclassifiedIPv460
AS57721Flash Networks Ltd.UnclassifiedIPv460
AS204395Elcam Medical Agricultural Cooperative Association LtdUnclassifiedIPv460
AS213055MyHeritage LtdUnclassifiedIPv460

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS25003Internet Binat LtdUnclassifiedIPv42,186
AS28783Netafim LTDUnclassifiedIPv4180
AS48068VISONIC LIMITEDUnclassifiedIPv4180
AS49069AspireGlobal Marketing Solutions LtdUnclassifiedIPv461
AS206531B.D.I.-COFACE LTDUnclassifiedIPv461
AS47461Starhome Mach GmbHUnclassifiedIPv460
AS47766Haifa Port Company LtdUnclassifiedIPv460
AS50865AMIAD WATER SYSTEMS LTDUnclassifiedIPv460
AS57721Flash Networks Ltd.UnclassifiedIPv460
AS204395Elcam Medical Agricultural Cooperative Association LtdUnclassifiedIPv460

Provenance

Where this comes from

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