Network · data from 2026-11-12
AS269581 Marcelo & Renato Digital Net LTDA
Registry name: AS269581 - Marcelo & Renato Digital Net LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269581, 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:66c4::/34 | No ROA | Nonecovered by 2804:66c4::/33 | 2 0%low visibility |
| 2804:66c4:4000::/34 | No ROA | Nonecovered by 2804:66c4::/33 | 2 0%low visibility |
| 45.188.156.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 45.188.156.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 45.188.158.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 45.188.157.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 2804:66c4:8000::/33 | No ROA | Other IRR onlyRADB | 635 100% |
| 45.188.158.0/24 | No ROA | Other IRR onlyRADB | 3 0%low visibility |
| 45.188.159.0/24 | No ROA | Other IRR onlyRADB | 3 0%low visibility |
| 2804:66c4::/33 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
AS269581'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 22 are in fix.csv.
- ROA: none10
- Route object: none2
- Route object: RIR8
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:66c4::/34 | No ROA covers it. Add a ROA for AS269581, maxLength 34. |
| Route object: none | 2804:66c4::/34 | No route object for it. A route object for 2804:66c4::/33 with origin AS269581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269581 in the RIR database for the space. |
| ROA: none | 2804:66c4:4000::/34 | No ROA covers it. Add a ROA for AS269581, maxLength 34. |
| Route object: none | 2804:66c4:4000::/34 | No route object for it. A route object for 2804:66c4::/33 with origin AS269581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269581 in the RIR database for the space. |
| ROA: none | 45.188.156.0/23 | No ROA covers it. Add a ROA for AS269581, maxLength 23. |
| Route object: RIR | 45.188.156.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.188.156.0/24 | No ROA covers it. Add a ROA for AS269581, maxLength 24. |
| Route object: RIR | 45.188.156.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.188.158.0/23 | No ROA covers it. Add a ROA for AS269581, maxLength 23. |
| Route object: RIR | 45.188.158.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.188.157.0/24 | No ROA covers it. Add a ROA for AS269581, maxLength 24. |
| Route object: RIR | 45.188.157.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:66c4:8000::/33 | No ROA covers it. Add a ROA for AS269581, maxLength 33. |
| Route object: RIR | 2804:66c4:8000::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.188.158.0/24 | No ROA covers it. Add a ROA for AS269581, maxLength 24. |
| Route object: RIR | 45.188.158.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.188.159.0/24 | No ROA covers it. Add a ROA for AS269581, maxLength 24. |
| Route object: RIR | 45.188.159.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:66c4::/33 | No ROA covers it. Add a ROA for AS269581, maxLength 33. |
| Route object: RIR | 2804:66c4::/33 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269581 whose prefix no peer sees AS269581 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.188.156.0/22 | TC | No ROA |
| 2804:66c4::/32 | 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.