Network · data from 2026-11-12

AS208095 INTERNETTEN TEKNOLOJI

Registry name: INTERNETTEN-TEKNOLOJI Internetten Teknoloji Bilisim Sanayi ve Ticaret Ltd. Sti., TR · PeeringDB

3IPv4 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

1Route objects not announced registered with origin AS208095, seen from no peer

Announced routes

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


94.124.73.0/24	Valid	RIR databaseRIPE	672 100%	67
45.159.28.0/24	Valid	RIR databaseRIPE	671 100%	67
45.159.29.0/24	Valid	RIR databaseRIPE	671 100%	67

AS-SET

PeeringDB's irr_as_set for AS208095: AS-WI. 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 (AS208095 isn't in the set, or no route object for AS208095 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	AS208095 in it	Not covered
AS-WI	RIPE2 member sets in no database: AS-BIRKACSEY, AS-COMNETINT	1	1	9	No	3

Name

Database

ASNs

Sets

Route objects

AS208095 in it

Not covered

AS-WI

RIPE2 member sets in no database: AS-BIRKACSEY, AS-COMNETINT

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 4 are in fix.csv.

AS-SET: own ASN1
AS-SET: missing member2
Route object: not announced1

Change	Prefix or set	Detail
AS-SET: own ASN	AS-WI	AS208095 isn't in AS-WI (RIPE) once expanded. Add AS208095 to it.
AS-SET: missing member	AS-WI	AS-WI (RIPE) lists AS-BIRKACSEY; no IRR database read has it.
AS-SET: missing member	AS-WI	AS-WI (RIPE) lists AS-COMNETINT; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

AS-SET: own ASN

AS-WI

AS208095 isn't in AS-WI (RIPE) once expanded. Add AS208095 to it.

AS-SET: missing member

AS-WI

AS-WI (RIPE) lists AS-BIRKACSEY; no IRR database read has it.

AS-SET: missing member

AS-WI

AS-WI (RIPE) lists AS-COMNETINT; no IRR database read has it.

Route objects not announced

Route objects with origin AS208095 whose prefix no peer sees AS208095 announce. Many are kept on purpose (backup routes, space announced only in some places).


2a0f:67c0::/48	RIPE	Valid

2a0f:67c0::/48

RIPE

Valid

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.