Network · data from 2026-11-12
AS269736 AS269736 - PACIFIC NETWORK COMMUNICATION S.A.
Registry name: AS269736 - PACIFIC NETWORK COMMUNICATION S.A., PA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269736, 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.181.68.0/24 | Valid | Nonecovered by 45.181.68.0/22 | 666 99% |
| 45.181.69.0/24 | Valid | Nonecovered by 45.181.68.0/22 | 666 99% |
| 45.181.70.0/24 | Valid | Nonecovered by 45.181.68.0/22 | 666 99% |
| 45.181.71.0/24 | Valid | Nonecovered by 45.181.68.0/22 | 666 99% |
| 45.181.68.0/22 | Valid | RIR databaseLACNIC, RADB | 666 99% |
| 2803:8960::/32 | Valid | RIR databaseLACNIC, RADB | 633 100% |
AS-SET
AS269736 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 11 are in fix.csv.
- Route object: none4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.181.68.0/24 | No route object for it. A route object for 45.181.68.0/22 with origin AS269736 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269736 in the RIR database for the space. |
| Route object: none | 45.181.69.0/24 | No route object for it. A route object for 45.181.68.0/22 with origin AS269736 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269736 in the RIR database for the space. |
| Route object: none | 45.181.70.0/24 | No route object for it. A route object for 45.181.68.0/22 with origin AS269736 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269736 in the RIR database for the space. |
| Route object: none | 45.181.71.0/24 | No route object for it. A route object for 45.181.68.0/22 with origin AS269736 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269736 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269736 whose prefix no peer sees AS269736 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2803:8960::/43 | LACNIC | Valid |
| 2803:8960:20::/48 | LACNIC | Valid |
| 2803:8960:100::/48 | LACNIC | Valid |
| 2803:8960:101::/48 | LACNIC | Valid |
| 2803:8960:102::/48 | LACNIC | Valid |
| 2803:8960:103::/48 | LACNIC | Valid |
| 2803:8960:104::/48 | 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.