Network · data from 2026-11-12
AS27727 AS27727 - Consultronic S.A.E.C.A.
Registry name: AS27727 - Consultronic S.A.E.C.A., PY · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS27727, 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.
| 200.61.232.0/24 | Valid | Nonecovered by 200.61.224.0/20 | 3 0%low visibility |
| 200.61.224.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 200.61.225.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 200.61.226.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 200.61.227.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 200.61.228.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 200.61.229.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 200.61.230.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 200.61.231.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 200.61.233.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 200.61.234.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 200.61.235.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 200.61.236.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 200.61.238.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 200.61.239.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
AS-SET
AS27727 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 18 are in fix.csv.
- Route object: none1
- Route object: RIR14
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 200.61.232.0/24 | No route object for it. A route object for 200.61.224.0/20 with origin AS27727 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27727 in the RIR database for the space. |
| Route object: RIR | 200.61.224.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.61.225.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.61.226.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.61.227.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.61.228.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.61.229.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.61.230.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.61.231.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.61.233.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.61.234.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.61.235.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.61.236.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.61.238.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.61.239.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS27727 whose prefix no peer sees AS27727 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 65.202.98.0/24 | ARIN | No ROA |
| 200.61.224.0/20 | RADB | No ROA |
| 200.61.237.0/24 | RADB | 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.