Network · data from 2026-11-12
AS264787 ANDRES POZZI
Registry name: AS264787 - ANDRES POZZI (PUNTONETINTERNET), AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264787, 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.
| 2803:d8c0:1000::/36 | Invalid: maxLength | Nonecovered by 2803:d8c0::/34 | 7 1%low visibility |
| 2803:d8c0:2000::/36 | Invalid: maxLength | Nonecovered by 2803:d8c0::/34 | 7 1%low visibility |
| 2803:d8c0:3000::/36 | Invalid: maxLength | Nonecovered by 2803:d8c0::/34 | 7 1%low visibility |
| 168.197.196.0/24 | Valid | Nonecovered by 168.197.196.0/23 | 672 100% |
| 168.197.197.0/24 | Valid | Nonecovered by 168.197.196.0/23 | 670 100% |
| 168.197.199.0/24 | Valid | Nonecovered by 168.197.196.0/22 | 670 100% |
| 168.197.198.0/24 | Valid | Other IRR onlyRADB | 673 100% |
AS-SET
AS264787's PeeringDB record names no 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 16 are in fix.csv.
- ROA: maxLength3
- Route object: none6
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2803:d8c0:1000::/36 | ROA 2803:d8c0::/34 AS264787 has maxLength 34; the route is a /36. Raise the maxLength, or add a ROA for 2803:d8c0:1000::/36. |
| Route object: none | 2803:d8c0:1000::/36 | No route object for it. A route object for 2803:d8c0::/34 with origin AS264787 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264787 in the RIR database for the space. |
| ROA: maxLength | 2803:d8c0:2000::/36 | ROA 2803:d8c0::/34 AS264787 has maxLength 34; the route is a /36. Raise the maxLength, or add a ROA for 2803:d8c0:2000::/36. |
| Route object: none | 2803:d8c0:2000::/36 | No route object for it. A route object for 2803:d8c0::/34 with origin AS264787 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264787 in the RIR database for the space. |
| ROA: maxLength | 2803:d8c0:3000::/36 | ROA 2803:d8c0::/34 AS264787 has maxLength 34; the route is a /36. Raise the maxLength, or add a ROA for 2803:d8c0:3000::/36. |
| Route object: none | 2803:d8c0:3000::/36 | No route object for it. A route object for 2803:d8c0::/34 with origin AS264787 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264787 in the RIR database for the space. |
| Route object: none | 168.197.196.0/24 | No route object for it. A route object for 168.197.196.0/23 with origin AS264787 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264787 in the RIR database for the space. |
| Route object: none | 168.197.197.0/24 | No route object for it. A route object for 168.197.196.0/23 with origin AS264787 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264787 in the RIR database for the space. |
| Route object: none | 168.197.199.0/24 | No route object for it. A route object for 168.197.196.0/22 with origin AS264787 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264787 in the RIR database for the space. |
| Route object: RIR | 168.197.198.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS264787 whose prefix no peer sees AS264787 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.197.196.0/22 | LACNIC, RADB | Valid |
| 168.197.196.0/23 | RADB | Valid |
| 2803:d8c0::/34 | LACNIC | Valid |
| 2803:d8c0::/40 | LACNIC | Valid |
| 2803:d8c0:4000::/34 | LACNIC | Valid |
| 2803:d8c0:8000::/34 | 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.