Network · data from 2026-11-12
AS213751 YALNIZ YALNIZ BILISIM TEKNOLOJILERI TIC. LTD.STI.
Registry name: YALNIZ YALNIZ BILISIM TEKNOLOJILERI TIC. LTD.STI., TR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213751, 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.177.27.0/24 | Invalid: origin | None | 2 0%low visibility |
| 5.56.30.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.76.162.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.124.124.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a14:9400:666::/48 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
AS213751 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 2 are in fix.csv.
- ROA: origin1
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.177.27.0/24 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS213751 should announce it, add a ROA for AS213751. |
| Route object: none | 185.177.27.0/24 | No route object for it. Add a route object with origin AS213751 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS213751 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.