Network · data from 2026-11-12

AS206938 NESILDC

Registry name: NESILDC Nesildc Bilisim Cozumleri Sanayi Ve Ticaret Limited Sirketi, TR · PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object

9IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS206938, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS206938, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


154.193.196.0/24	Valid	RIR databaseAFRINIC, RADB	672 100%	66
212.22.69.0/24	Valid	RIR databaseRIPE	672 100%	66
45.196.132.0/24	Valid	RIR databaseAFRINIC, RADB	670 100%	66
2a07:4a00::/32	Valid	RIR databaseRIPE	634 100%	67
2a14:4b80::/32	Valid	RIR databaseRIPE	632 99%	67
2a14:4b81::/32	Valid	RIR databaseRIPE	632 99%	67
2a14:4b82::/32	Valid	RIR databaseRIPE	632 99%	67
2a14:4b83::/32	Valid	RIR databaseRIPE	632 99%	67
2a14:4b84::/32	Valid	RIR databaseRIPE	632 99%	67
2a14:4b85::/32	Valid	RIR databaseRIPE	631 99%	67
2a14:4b86::/32	Valid	RIR databaseRIPE	631 99%	67
2a14:4b87::/32	Valid	RIR databaseRIPE	631 99%	67

AS-SET

AS206938's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS206938 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.