bgpreport

Network · data from 2026-11-12

AS212269 AS-Aytelekom AY TELEKOM BILGI TEKNOLOJILERI LIMITED SIRKETI

Registry name: AS-Aytelekom AY TELEKOM BILGI TEKNOLOJILERI LIMITED SIRKETI, TR · not in PeeringDB

3IPv4 routes 66.7% RPKI valid · 100.0% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
0No ROA 0 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS212269, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS212269, 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.
194.37.92.0/24 Invalid: origin RIR databaseRIPE 5 1%low visibility 5
194.5.232.0/24 Valid RIR databaseRIPE 673 100% 67
185.179.100.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS212269 isn't in PeeringDB, where networks name their AS-SET.

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.

  • ROA: origin1
ChangePrefix or setDetailFull-table peers
ROA: origin194.37.92.0/24ROAs covering it name AS200404, not AS212269. If AS212269 should announce it, add a ROA for AS212269.5 of 673

Route objects not announced

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