Network · data from 2026-11-12
AS267288 PONGAR TELECOM
Registry name: AS267288 - PONGAR TELECOM, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267288, 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.
| 2804:4b2c::/33 | No ROA | Nonecovered by 2804:4b2c::/32 | 636 100% |
| 2804:4b2c:8000::/33 | No ROA | Nonecovered by 2804:4b2c::/32 | 636 100% |
| 45.233.16.0/22 | No ROA | Other IRR onlyALTDB, NTTCOM, RADB | 671 100% |
| 45.233.16.0/23 | No ROA | Other IRR onlyALTDB | 671 100% |
| 45.233.18.0/23 | No ROA | Other IRR onlyALTDB | 671 100% |
| 45.233.16.0/24 | No ROA | Other IRR onlyALTDB | 668 99% |
| 45.233.17.0/24 | No ROA | Other IRR onlyALTDB | 668 99% |
| 45.233.18.0/24 | No ROA | Other IRR onlyALTDB | 668 99% |
| 45.233.19.0/24 | No ROA | Other IRR onlyALTDB | 668 99% |
| 2804:4b2c::/32 | No ROA | Other IRR onlyALTDB, NTTCOM, RADB | 636 100% |
AS-SET
AS267288'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 21 are in fix.csv.
- ROA: none10
- Route object: none2
- Route object: RIR8
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:4b2c::/33 | No ROA covers it. Add a ROA for AS267288, maxLength 33. |
| Route object: none | 2804:4b2c::/33 | No route object for it. A route object for 2804:4b2c::/32 with origin AS267288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267288 in the RIR database for the space. |
| ROA: none | 2804:4b2c:8000::/33 | No ROA covers it. Add a ROA for AS267288, maxLength 33. |
| Route object: none | 2804:4b2c:8000::/33 | No route object for it. A route object for 2804:4b2c::/32 with origin AS267288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267288 in the RIR database for the space. |
| ROA: none | 45.233.16.0/22 | No ROA covers it. Add a ROA for AS267288, maxLength 22. |
| Route object: RIR | 45.233.16.0/22 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 45.233.16.0/23 | No ROA covers it. Add a ROA for AS267288, maxLength 23. |
| Route object: RIR | 45.233.16.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 45.233.18.0/23 | No ROA covers it. Add a ROA for AS267288, maxLength 23. |
| Route object: RIR | 45.233.18.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 45.233.16.0/24 | No ROA covers it. Add a ROA for AS267288, maxLength 24. |
| Route object: RIR | 45.233.16.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 45.233.17.0/24 | No ROA covers it. Add a ROA for AS267288, maxLength 24. |
| Route object: RIR | 45.233.17.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 45.233.18.0/24 | No ROA covers it. Add a ROA for AS267288, maxLength 24. |
| Route object: RIR | 45.233.18.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 45.233.19.0/24 | No ROA covers it. Add a ROA for AS267288, maxLength 24. |
| Route object: RIR | 45.233.19.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 2804:4b2c::/32 | No ROA covers it. Add a ROA for AS267288, maxLength 32. |
| Route object: RIR | 2804:4b2c::/32 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267288 whose prefix no peer sees AS267288 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.86.39.0/24 | NTTCOM | No ROA |
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.