Network · data from 2026-11-12
AS204249 PAIK-LTD "PAIK" Company for Communication and General Trade Importation& Exportation Limited
Registry name: PAIK-LTD "PAIK" Company for Communication and General Trade Importation& Exportation Limited, IQ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS204249, 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.
| 2a00:f7a0:100::/48 | Valid | None | 631 99% |
| 185.54.164.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.54.165.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.54.166.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.54.167.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS204249 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 5 are in fix.csv.
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a00:f7a0:100::/48 | No route object for it. Add a route object with origin AS204249 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS204249 whose prefix no peer sees AS204249 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.37.160.0/22 | RIPE | Invalid: origin |
| 185.37.162.0/24 | RIPE | Valid |
| 185.54.164.0/22 | RIPE | No ROA |
| 185.54.166.0/23 | 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.