asn.dev

Observed topology

AS203545 NERZEN-BILISIM-TEKNOLOJILERI Savas Anac

Unclassified ARIN Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS203545: 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
AS199524G-Core Labs S.A.HostingIPv4354
AS212219HOSTING DUNYAM BILISIM TEKNOLOJILERI TICARET LIMITED SIRKETIHostingIPv636
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213796Ahmet CevikUnclassifiedIPv4 IPv6172
AS198988Vode Soft LLCUnclassifiedIPv4122

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS199524G-Core Labs S.A.HostingIPv4414
AS213796Ahmet CevikUnclassifiedIPv4 IPv6172
AS198988Vode Soft LLCUnclassifiedIPv4122
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv6120
AS218802Northshield LLCUnclassifiedIPv4120
AS212219HOSTING DUNYAM BILISIM TEKNOLOJILERI TICARET LIMITED SIRKETIHostingIPv636

Provenance

Where this comes from

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