Network · data from 2026-11-12
AS12599 ATLAS-AS Atlas On-Line Iletisim Sistemleri ve Tic. A.S.
Registry name: ATLAS-AS Atlas On-Line Iletisim Sistemleri ve Tic. A.S., TR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12599, 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.64.194.0/24 | Valid | Nonecovered by 212.64.192.0/21 | 671 100% |
| 212.64.197.0/24 | Valid | Nonecovered by 212.64.192.0/21 | 671 100% |
| 212.64.198.0/24 | Valid | Nonecovered by 212.64.192.0/21 | 671 100% |
| 212.64.200.0/24 | Valid | Nonecovered by 212.64.200.0/21 | 671 100% |
| 212.64.203.0/24 | Valid | Nonecovered by 212.64.200.0/21 | 671 100% |
| 212.64.204.0/24 | Valid | Nonecovered by 212.64.200.0/21 | 671 100% |
| 212.64.205.0/24 | Valid | Nonecovered by 212.64.200.0/21 | 671 100% |
| 212.64.206.0/24 | Valid | Nonecovered by 212.64.200.0/21 | 671 100% |
| 212.64.207.0/24 | Valid | Nonecovered by 212.64.200.0/21 | 671 100% |
| 212.64.209.0/24 | Valid | Nonecovered by 212.64.208.0/21 | 671 100% |
| 212.64.220.0/24 | Valid | Nonecovered by 212.64.216.0/21 | 671 100% |
AS-SET
AS12599 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 15 are in fix.csv.
- Route object: none11
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 212.64.194.0/24 | No route object for it. A route object for 212.64.192.0/21 with origin AS12599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12599 in the RIR database for the space. |
| Route object: none | 212.64.197.0/24 | No route object for it. A route object for 212.64.192.0/21 with origin AS12599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12599 in the RIR database for the space. |
| Route object: none | 212.64.198.0/24 | No route object for it. A route object for 212.64.192.0/21 with origin AS12599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12599 in the RIR database for the space. |
| Route object: none | 212.64.200.0/24 | No route object for it. A route object for 212.64.200.0/21 with origin AS12599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12599 in the RIR database for the space. |
| Route object: none | 212.64.203.0/24 | No route object for it. A route object for 212.64.200.0/21 with origin AS12599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12599 in the RIR database for the space. |
| Route object: none | 212.64.204.0/24 | No route object for it. A route object for 212.64.200.0/21 with origin AS12599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12599 in the RIR database for the space. |
| Route object: none | 212.64.205.0/24 | No route object for it. A route object for 212.64.200.0/21 with origin AS12599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12599 in the RIR database for the space. |
| Route object: none | 212.64.206.0/24 | No route object for it. A route object for 212.64.200.0/21 with origin AS12599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12599 in the RIR database for the space. |
| Route object: none | 212.64.207.0/24 | No route object for it. A route object for 212.64.200.0/21 with origin AS12599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12599 in the RIR database for the space. |
| Route object: none | 212.64.209.0/24 | No route object for it. A route object for 212.64.208.0/21 with origin AS12599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12599 in the RIR database for the space. |
| Route object: none | 212.64.220.0/24 | No route object for it. A route object for 212.64.216.0/21 with origin AS12599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12599 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS12599 whose prefix no peer sees AS12599 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 212.64.192.0/21 | RIPE | No ROA |
| 212.64.200.0/21 | RIPE | No ROA |
| 212.64.208.0/21 | RIPE | No ROA |
| 212.64.216.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.