Network · data from 2026-11-12
AS262872 Digicontrol
Registry name: AS262872 - DIGICONTROL SERVICOS DE PROVEDORES LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS262872, 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.11.64.0/21 | Valid | Other IRR onlyNTTCOM, RADB, TC | 672 100% |
| 177.11.64.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.11.68.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.11.64.0/23 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 177.11.66.0/23 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 177.11.68.0/23 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 177.11.69.0/24 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 177.11.70.0/23 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 177.11.65.0/24 | Valid | Other IRR onlyRADB, TC | 660 98% |
| 177.11.70.0/24 | Valid | Other IRR onlyTC | 660 98% |
| 177.11.71.0/24 | Valid | Other IRR onlyRADB, TC | 660 98% |
| 2804:9b4::/32 | Valid | Other IRR onlyNTTCOM, RADB, TC | 632 99% |
| 2804:9b4::/33 | Valid | Other IRR onlyRADB, TC | 627 99% |
| 2804:9b4:8000::/33 | Valid | Other IRR onlyRADB, TC | 627 99% |
| 2804:9b4:8000::/34 | Valid | Other IRR onlyTC | 307 48% |
| 2804:9b4::/34 | Valid | Other IRR onlyTC | 306 48% |
| 2804:9b4:4000::/34 | Valid | Other IRR onlyTC | 306 48% |
| 2804:9b4:c000::/34 | Valid | Other IRR onlyTC | 306 48% |
| 177.11.67.0/24 | Valid | Other IRR onlyRADB, TC | 100 15% |
| 177.11.64.0/24 | Valid | Other IRR onlyRADB, TC | 99 15% |
| 177.11.66.0/24 | Valid | Other IRR onlyRADB, TC | 99 15% |
| 177.11.68.0/24 | Valid | Other IRR onlyRADB, TC | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS262872: AS262872:AS-ANNOUNCEMENTS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS262872 isn't in the set, or no route object for AS262872 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS262872 in it | Not covered |
|---|---|---|---|---|---|
| AS262872:AS-ANNOUNCEMENTS | TC | 9 | 2 | Yes | 0 |
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 23 are in fix.csv.
- Route object: RIR22
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 177.11.64.0/21 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.11.64.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.11.68.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.11.64.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.11.66.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.11.68.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.11.69.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.11.70.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.11.65.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.11.70.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.11.71.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9b4::/32 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9b4::/33 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9b4:8000::/33 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9b4:8000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9b4::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9b4:4000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9b4:c000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.11.67.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.11.64.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.11.66.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.11.68.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS262872 whose prefix no peer sees AS262872 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:2bec::/32 | 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.