Network · data from 2026-11-12
AS262445 AS262445 - SulDigital Internet Ltda ME
Registry name: AS262445 - SulDigital Internet Ltda ME, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS262445, 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.52.112.0/23 | No ROA | Nonecovered by 177.52.112.0/22 | 672 100% |
| 177.52.114.0/23 | No ROA | Nonecovered by 177.52.112.0/22 | 671 100% |
| 177.52.118.0/23 | No ROA | Nonecovered by 177.52.116.0/22 | 671 100% |
| 177.52.112.0/22 | No ROA | Other IRR onlyTC | 672 100% |
| 177.52.116.0/24 | No ROA | Other IRR onlyTC | 672 100% |
| 177.52.117.0/24 | No ROA | Other IRR onlyTC | 672 100% |
| 2804:484::/32 | No ROA | Other IRR onlyRADB, TC | 636 100% |
| 177.52.118.0/24 | No ROA | Other IRR onlyTC | 2 0%low visibility |
| 177.52.119.0/24 | No ROA | Other IRR onlyTC | 2 0%low visibility |
AS-SET
AS262445 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 24 are in fix.csv.
- ROA: none9
- Route object: none3
- Route object: RIR6
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 177.52.112.0/23 | No ROA covers it. Add a ROA for AS262445, maxLength 23. |
| Route object: none | 177.52.112.0/23 | No route object for it. A route object for 177.52.112.0/22 with origin AS262445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262445 in the RIR database for the space. |
| ROA: none | 177.52.114.0/23 | No ROA covers it. Add a ROA for AS262445, maxLength 23. |
| Route object: none | 177.52.114.0/23 | No route object for it. A route object for 177.52.112.0/22 with origin AS262445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262445 in the RIR database for the space. |
| ROA: none | 177.52.118.0/23 | No ROA covers it. Add a ROA for AS262445, maxLength 23. |
| Route object: none | 177.52.118.0/23 | No route object for it. A route object for 177.52.116.0/22 with origin AS262445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262445 in the RIR database for the space. |
| ROA: none | 177.52.112.0/22 | No ROA covers it. Add a ROA for AS262445, maxLength 22. |
| Route object: RIR | 177.52.112.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 177.52.116.0/24 | No ROA covers it. Add a ROA for AS262445, maxLength 24. |
| Route object: RIR | 177.52.116.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 177.52.117.0/24 | No ROA covers it. Add a ROA for AS262445, maxLength 24. |
| Route object: RIR | 177.52.117.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 2804:484::/32 | No ROA covers it. Add a ROA for AS262445, maxLength 32. |
| Route object: RIR | 2804:484::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 177.52.118.0/24 | No ROA covers it. Add a ROA for AS262445, maxLength 24. |
| Route object: RIR | 177.52.118.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 177.52.119.0/24 | No ROA covers it. Add a ROA for AS262445, maxLength 24. |
| Route object: RIR | 177.52.119.0/24 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS262445 whose prefix no peer sees AS262445 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.52.112.0/21 | RADB, TC | No ROA |
| 177.52.112.0/24 | TC | No ROA |
| 177.52.113.0/24 | TC | No ROA |
| 177.52.114.0/24 | TC | No ROA |
| 177.52.115.0/24 | TC | No ROA |
| 177.52.116.0/22 | 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.