Network · data from 2026-11-12
AS266469 AS266469 - PROVWEB JANDER FORTES LIMA - ME
Registry name: AS266469 - PROVWEB JANDER FORTES LIMA - ME, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS266469, 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.
| 170.83.148.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 170.83.150.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
| 170.83.151.0/24 | No ROA | Other IRR onlyRADB | 666 99% |
| 2804:3850::/34 | No ROA | Other IRR onlyRADB | 636 100% |
| 2804:3850:4000::/34 | No ROA | Other IRR onlyRADB | 636 100% |
| 2804:3850:8000::/34 | No ROA | Other IRR onlyRADB | 636 100% |
| 2804:3850:c000::/34 | No ROA | Other IRR onlyRADB | 635 100% |
| 2804:3850:c000::/35 | No ROA | Other IRR onlyRADB | 635 100% |
| 2804:3850:e000::/35 | No ROA | Other IRR onlyRADB | 635 100% |
AS-SET
AS266469 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 31 are in fix.csv.
- ROA: none9
- Route object: RIR9
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 170.83.148.0/23 | No ROA covers it. Add a ROA for AS266469, maxLength 23. |
| Route object: RIR | 170.83.148.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 170.83.150.0/24 | No ROA covers it. Add a ROA for AS266469, maxLength 24. |
| Route object: RIR | 170.83.150.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 170.83.151.0/24 | No ROA covers it. Add a ROA for AS266469, maxLength 24. |
| Route object: RIR | 170.83.151.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:3850::/34 | No ROA covers it. Add a ROA for AS266469, maxLength 34. |
| Route object: RIR | 2804:3850::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:3850:4000::/34 | No ROA covers it. Add a ROA for AS266469, maxLength 34. |
| Route object: RIR | 2804:3850:4000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:3850:8000::/34 | No ROA covers it. Add a ROA for AS266469, maxLength 34. |
| Route object: RIR | 2804:3850:8000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:3850:c000::/34 | No ROA covers it. Add a ROA for AS266469, maxLength 34. |
| Route object: RIR | 2804:3850:c000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:3850:c000::/35 | No ROA covers it. Add a ROA for AS266469, maxLength 35. |
| Route object: RIR | 2804:3850:c000::/35 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:3850:e000::/35 | No ROA covers it. Add a ROA for AS266469, maxLength 35. |
| Route object: RIR | 2804:3850:e000::/35 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS266469 whose prefix no peer sees AS266469 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 170.83.148.0/22 | RADB | No ROA |
| 170.83.148.0/24 | RADB | No ROA |
| 170.83.149.0/24 | RADB | No ROA |
| 170.83.150.0/23 | RADB | No ROA |
| 2804:3850::/32 | RADB | No ROA |
| 2804:3850::/33 | RADB | No ROA |
| 2804:3850:100::/40 | RADB | No ROA |
| 2804:3850:200::/40 | RADB | No ROA |
| 2804:3850:300::/40 | RADB | No ROA |
| 2804:3850:8000::/33 | RADB | No ROA |
| 2804:3850:8000::/36 | RADB | No ROA |
| 2804:3850:8000::/40 | RADB | No ROA |
| 2804:3850:8100::/40 | RADB | 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.