Network · data from 2026-11-12
AS263294 AS263294 - NOVELTY TELECOM LTDA
Registry name: AS263294 - NOVELTY TELECOM LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263294, 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.
| 177.47.92.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 177.47.92.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 177.47.94.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 177.47.88.0/23 | No ROA | Other IRR onlyRADB | 670 100% |
| 177.47.89.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 177.47.90.0/23 | No ROA | Other IRR onlyRADB | 670 100% |
| 177.47.90.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 177.47.91.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 177.47.88.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
| 2804:1694:1000::/36 | No ROA | Other IRR onlyRADB | 632 99% |
| 2804:1694:8000::/34 | No ROA | Other IRR onlyRADB | 632 99% |
AS-SET
AS263294 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 28 are in fix.csv.
- ROA: none11
- Route object: RIR11
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 177.47.92.0/22 | No ROA covers it. Add a ROA for AS263294, maxLength 22. |
| Route object: RIR | 177.47.92.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.47.92.0/23 | No ROA covers it. Add a ROA for AS263294, maxLength 23. |
| Route object: RIR | 177.47.92.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.47.94.0/23 | No ROA covers it. Add a ROA for AS263294, maxLength 23. |
| Route object: RIR | 177.47.94.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.47.88.0/23 | No ROA covers it. Add a ROA for AS263294, maxLength 23. |
| Route object: RIR | 177.47.88.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.47.89.0/24 | No ROA covers it. Add a ROA for AS263294, maxLength 24. |
| Route object: RIR | 177.47.89.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.47.90.0/23 | No ROA covers it. Add a ROA for AS263294, maxLength 23. |
| Route object: RIR | 177.47.90.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.47.90.0/24 | No ROA covers it. Add a ROA for AS263294, maxLength 24. |
| Route object: RIR | 177.47.90.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.47.91.0/24 | No ROA covers it. Add a ROA for AS263294, maxLength 24. |
| Route object: RIR | 177.47.91.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.47.88.0/24 | No ROA covers it. Add a ROA for AS263294, maxLength 24. |
| Route object: RIR | 177.47.88.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:1694:1000::/36 | No ROA covers it. Add a ROA for AS263294, maxLength 36. |
| Route object: RIR | 2804:1694:1000::/36 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:1694:8000::/34 | No ROA covers it. Add a ROA for AS263294, maxLength 34. |
| Route object: RIR | 2804:1694:8000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263294 whose prefix no peer sees AS263294 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.47.88.0/21 | RADB, TC | No ROA |
| 177.47.92.0/24 | RADB | No ROA |
| 177.47.93.0/24 | RADB | No ROA |
| 177.47.94.0/24 | RADB | No ROA |
| 177.47.95.0/24 | RADB | No ROA |
| 2804:1694::/32 | RADB, TC | 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.