Network · data from 2026-11-12
AS59625 KorekTel Korek Telecom Company for Communications LLC
Registry name: KorekTel Korek Telecom Company for Communications LLC, IQ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59625, 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.
| 2a03:7020::/48 | Valid | Nonecovered by 2a03:7020::/40 | 635 100% |
| 185.84.68.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.84.69.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.84.70.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.84.71.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.240.16.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.240.17.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.240.18.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.240.19.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 204.154.201.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 204.154.202.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 204.154.203.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 204.154.204.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a03:7020::/40 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:7020:1::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:7020:10::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:7020:100::/40 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:7020:300::/40 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:7020:800::/40 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:7020:1300::/40 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS59625 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 24 are in fix.csv.
- Route object: none1
- Route object: not announced23
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a03:7020::/48 | No route object for it. A route object for 2a03:7020::/40 with origin AS59625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59625 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS59625 whose prefix no peer sees AS59625 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.244.176.0/24 | RIPE | Valid |
| 185.244.178.0/24 | RIPE | Valid |
| 185.244.179.0/24 | RIPE | Valid |
| 204.154.200.0/24 | RIPE | Valid |
| 204.154.205.0/24 | RIPE | Valid |
| 204.154.206.0/24 | RIPE | Valid |
| 204.154.207.0/24 | RIPE | Valid |
| 2a03:7020::/32 | RIPE | No ROA |
| 2a03:7020:200::/40 | RIPE | No ROA |
| 2a03:7020:400::/40 | RIPE | No ROA |
| 2a03:7020:500::/40 | RIPE | No ROA |
| 2a03:7020:600::/40 | RIPE | No ROA |
| 2a03:7020:700::/40 | RIPE | No ROA |
| 2a03:7020:900::/40 | RIPE | No ROA |
| 2a03:7020:a00::/40 | RIPE | No ROA |
| 2a03:7020:b00::/40 | RIPE | No ROA |
| 2a03:7020:c00::/40 | RIPE | No ROA |
| 2a03:7020:d00::/40 | RIPE | No ROA |
| 2a03:7020:e00::/40 | RIPE | No ROA |
| 2a03:7020:f00::/40 | RIPE | No ROA |
| 2a03:7020:1000::/40 | RIPE | No ROA |
| 2a03:7020:1100::/40 | RIPE | No ROA |
| 2a03:7020:1200::/40 | 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.