Network · data from 2026-11-12
AS267841 AS267841 - GIGAS HOSTING COLOMBIA S.A.S.
Registry name: AS267841 - GIGAS HOSTING COLOMBIA S.A.S., CO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267841, 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.
| 168.232.32.0/22 | No ROA | Other origin only | 668 99% |
| 45.163.28.0/24 | Valid | RIR databaseLACNIC, RADB | 668 99% |
| 45.163.29.0/24 | Valid | RIR databaseLACNIC, RADB | 668 99% |
| 45.163.30.0/24 | Valid | RIR databaseLACNIC | 668 99% |
| 170.239.154.0/23 | Valid | RIR databaseLACNIC | 668 99% |
AS-SET
AS267841 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 4 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 168.232.32.0/22 | No ROA covers it. Add a ROA for AS267841, maxLength 22. |
| Route object: none | 168.232.32.0/22 | Route objects for it name AS14259. Add a route object with origin AS267841 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267841 whose prefix no peer sees AS267841 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.163.28.0/23 | RADB | No ROA |
| 2803:31a0::/32 | LACNIC | 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.