Network · data from 2026-11-12

AS206991 IXIR

Registry name: IXIR Iksir Internet Hizmetleri A.S., TR · PeeringDB

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

0IPv6 routes

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 AS206991, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS206991, 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.


185.169.64.0/24	Valid	RIR databaseRIPE	673 100%	66
85.95.237.0/24	Valid	RIR databaseRIPE	672 100%	66
85.95.238.0/24	Valid	RIR databaseRIPE	672 100%	66
85.95.239.0/24	Valid	RIR databaseRIPE	672 100%	66
85.95.240.0/24	Valid	RIR databaseRIPE	672 100%	66
85.95.241.0/24	Valid	RIR databaseRIPE	672 100%	66
85.95.242.0/24	Valid	RIR databaseRIPE	672 100%	66
85.95.243.0/24	Valid	RIR databaseRIPE	672 100%	66
85.95.244.0/24	Valid	RIR databaseRIPE	672 100%	66
185.123.100.0/24	Valid	RIR databaseRIPE	672 100%	66
185.123.101.0/24	Valid	RIR databaseRIPE	672 100%	66
185.169.65.0/24	Valid	RIR databaseRIPE	672 100%	66
185.169.66.0/24	Valid	RIR databaseRIPE	672 100%	66
185.169.67.0/24	Valid	RIR databaseRIPE	672 100%	66

AS-SET

PeeringDB's irr_as_set for AS206991: AS-IXIR. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS206991 isn't in the set, or no route object for AS206991 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS206991 in it	Not covered
AS-IXIR	RIPE	271	9	19,340	No	14

Name

Database

ASNs

Sets

Route objects

AS206991 in it

Not covered

AS-IXIR

RIPE

271

19,340

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 1 are in fix.csv.

AS-SET: own ASN1

Change	Prefix or set	Detail	Full-table peers
AS-SET: own ASN	AS-IXIR	AS206991 isn't in AS-IXIR (RIPE) once expanded. Add AS206991 to it.

Change

Prefix or set

Detail

Full-table peers

AS-SET: own ASN

AS-IXIR

AS206991 isn't in AS-IXIR (RIPE) once expanded. Add AS206991 to it.

Route objects not announced

Every route object with origin AS206991 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.