Network · data from 2026-11-12
AS12840 TICARETNET ATP YAZILIM VE TEKNOLOJI A.S.
Registry name: TICARETNET ATP YAZILIM VE TEKNOLOJI A.S., TR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12840, 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.
| 212.109.122.0/24 | No ROA | Nonecovered by 212.109.120.0/21 | 672 100% |
| 212.109.124.0/22 | No ROA | Nonecovered by 212.109.120.0/21 | 672 100% |
| 212.109.116.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 212.109.120.0/23 | Valid | Nonecovered by 212.109.120.0/21 | 672 100% |
| 212.109.123.0/24 | Valid | Nonecovered by 212.109.120.0/21 | 672 100% |
| 212.109.96.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 212.109.112.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.109.113.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.109.114.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.109.115.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.109.96.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.109.98.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.109.100.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.109.102.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.109.103.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.109.107.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS12840 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 10 are in fix.csv.
- ROA: none3
- Route object: none4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 212.109.122.0/24 | No ROA covers it. Add a ROA for AS12840, maxLength 24. |
| Route object: none | 212.109.122.0/24 | No route object for it. A route object for 212.109.120.0/21 with origin AS12840 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12840 in the RIR database for the space. |
| ROA: none | 212.109.124.0/22 | No ROA covers it. Add a ROA for AS12840, maxLength 22. |
| Route object: none | 212.109.124.0/22 | No route object for it. A route object for 212.109.120.0/21 with origin AS12840 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12840 in the RIR database for the space. |
| ROA: none | 212.109.116.0/22 | No ROA covers it. Add a ROA for AS12840, maxLength 22. |
| Route object: none | 212.109.120.0/23 | No route object for it. A route object for 212.109.120.0/21 with origin AS12840 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12840 in the RIR database for the space. |
| Route object: none | 212.109.123.0/24 | No route object for it. A route object for 212.109.120.0/21 with origin AS12840 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12840 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS12840 whose prefix no peer sees AS12840 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 212.109.96.0/19 | RIPE | No ROA |
| 212.109.112.0/22 | RIPE | Valid |
| 212.109.120.0/21 | RIPE | No ROA |
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.