Network · data from 2026-11-12
AS267807 AS267807 - PSI TELECOMUNICACIONES DE COLOMBIA LTDA
Registry name: AS267807 - PSI TELECOMUNICACIONES DE COLOMBIA LTDA, CO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267807, 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.
| 45.173.68.0/24 | Valid | Nonecovered by 45.173.68.0/22 | 670 100% |
| 45.173.69.0/24 | Valid | Nonecovered by 45.173.68.0/22 | 670 100% |
| 45.173.70.0/24 | Valid | Nonecovered by 45.173.68.0/22 | 670 100% |
| 45.173.71.0/24 | Valid | Nonecovered by 45.173.68.0/22 | 670 100% |
| 2803:a060::/33 | Valid | Nonecovered by 2803:a060::/32 | 633 100% |
| 2803:a060:8000::/35 | Valid | Nonecovered by 2803:a060::/32 | 631 99% |
AS-SET
AS267807 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 8 are in fix.csv.
- Route object: none6
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.173.68.0/24 | No route object for it. A route object for 45.173.68.0/22 with origin AS267807 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267807 in the RIR database for the space. |
| Route object: none | 45.173.69.0/24 | No route object for it. A route object for 45.173.68.0/22 with origin AS267807 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267807 in the RIR database for the space. |
| Route object: none | 45.173.70.0/24 | No route object for it. A route object for 45.173.68.0/22 with origin AS267807 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267807 in the RIR database for the space. |
| Route object: none | 45.173.71.0/24 | No route object for it. A route object for 45.173.68.0/22 with origin AS267807 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267807 in the RIR database for the space. |
| Route object: none | 2803:a060::/33 | No route object for it. A route object for 2803:a060::/32 with origin AS267807 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267807 in the RIR database for the space. |
| Route object: none | 2803:a060:8000::/35 | No route object for it. A route object for 2803:a060::/32 with origin AS267807 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267807 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267807 whose prefix no peer sees AS267807 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.173.68.0/22 | RADB | Valid |
| 2803:a060::/32 | 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.