Network · data from 2026-11-12
AS11993 AS11993 - BANCO DO BRASIL S.A.
Registry name: AS11993 - BANCO DO BRASIL S.A., BR · not in PeeringDB
30IPv4 routes
100.0% RPKI valid · 3.3% with a route object
4IPv6 routes
100.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
33 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
3Route objects not announced
registered with origin AS11993, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS11993, 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.
| 201.33.149.0/24 | Valid | Nonecovered by 201.33.144.0/20 | 671 100% |
| 201.33.150.0/24 | Valid | Nonecovered by 201.33.144.0/20 | 671 100% |
| 201.33.152.0/24 | Valid | Nonecovered by 201.33.144.0/20 | 671 100% |
| 170.66.12.0/24 | Valid | Nonecovered by 170.66.0.0/16 | 670 100% |
| 170.66.110.0/24 | Valid | Nonecovered by 170.66.0.0/16 | 670 100% |
| 170.66.118.0/24 | Valid | Nonecovered by 170.66.0.0/16 | 670 100% |
| 170.66.128.0/18 | Valid | Nonecovered by 170.66.0.0/16 | 670 100% |
| 170.66.248.0/22 | Valid | Nonecovered by 170.66.0.0/16 | 670 100% |
| 201.33.144.0/24 | Valid | Nonecovered by 201.33.144.0/20 | 670 100% |
| 201.33.145.0/24 | Valid | Nonecovered by 201.33.144.0/20 | 670 100% |
| 201.33.146.0/24 | Valid | Nonecovered by 201.33.144.0/20 | 670 100% |
| 201.33.147.0/24 | Valid | Nonecovered by 201.33.144.0/20 | 670 100% |
| 201.33.148.0/24 | Valid | Nonecovered by 201.33.144.0/20 | 670 100% |
| 201.33.151.0/24 | Valid | Nonecovered by 201.33.144.0/20 | 670 100% |
| 201.33.153.0/24 | Valid | Nonecovered by 201.33.144.0/20 | 670 100% |
| 170.66.0.0/17 | Valid | Nonecovered by 170.66.0.0/16 | 669 99% |
| 170.66.2.0/24 | Valid | Nonecovered by 170.66.0.0/16 | 669 99% |
| 170.66.10.0/24 | Valid | Nonecovered by 170.66.0.0/16 | 669 99% |
| 170.66.11.0/24 | Valid | Nonecovered by 170.66.0.0/16 | 669 99% |
| 170.66.102.0/24 | Valid | Nonecovered by 170.66.0.0/16 | 669 99% |
| 170.66.117.0/24 | Valid | Nonecovered by 170.66.0.0/16 | 669 99% |
| 170.66.192.0/18 | Valid | Nonecovered by 170.66.0.0/16 | 669 99% |
| 170.66.192.0/24 | Valid | Nonecovered by 170.66.0.0/16 | 669 99% |
| 170.66.193.0/24 | Valid | Nonecovered by 170.66.0.0/16 | 669 99% |
| 170.66.194.0/24 | Valid | Nonecovered by 170.66.0.0/16 | 669 99% |
| 170.66.206.0/24 | Valid | Nonecovered by 170.66.0.0/16 | 669 99% |
| 170.66.217.0/24 | Valid | Nonecovered by 170.66.0.0/16 | 669 99% |
| 170.66.224.0/24 | Valid | Nonecovered by 170.66.0.0/16 | 669 99% |
| 170.66.196.0/24 | Valid | Nonecovered by 170.66.0.0/16 | 668 99% |
| 2801:8e::/36 | Valid | Nonecovered by 2801:8e::/32 | 636 100% |
| 2801:8e:a000::/36 | Valid | Nonecovered by 2801:8e::/32 | 636 100% |
| 2801:8e:804::/48 | Valid | Nonecovered by 2801:8e::/32 | 635 100% |
| 2801:8e:f000::/48 | Valid | Nonecovered by 2801:8e::/32 | 635 100% |
| 198.184.161.0/24 | Valid | Other IRR onlyRADB | 670 100% |
AS-SET
AS11993 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 37 are in fix.csv.
- Route object: none33
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 201.33.149.0/24 | No route object for it. A route object for 201.33.144.0/20 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 201.33.150.0/24 | No route object for it. A route object for 201.33.144.0/20 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 201.33.152.0/24 | No route object for it. A route object for 201.33.144.0/20 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.12.0/24 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.110.0/24 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.118.0/24 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.128.0/18 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.248.0/22 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 201.33.144.0/24 | No route object for it. A route object for 201.33.144.0/20 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 201.33.145.0/24 | No route object for it. A route object for 201.33.144.0/20 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 201.33.146.0/24 | No route object for it. A route object for 201.33.144.0/20 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 201.33.147.0/24 | No route object for it. A route object for 201.33.144.0/20 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 201.33.148.0/24 | No route object for it. A route object for 201.33.144.0/20 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 201.33.151.0/24 | No route object for it. A route object for 201.33.144.0/20 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 201.33.153.0/24 | No route object for it. A route object for 201.33.144.0/20 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.0.0/17 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.2.0/24 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.10.0/24 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.11.0/24 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.102.0/24 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.117.0/24 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.192.0/18 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.192.0/24 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.193.0/24 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.194.0/24 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.206.0/24 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.217.0/24 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.224.0/24 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 170.66.196.0/24 | No route object for it. A route object for 170.66.0.0/16 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 2801:8e::/36 | No route object for it. A route object for 2801:8e::/32 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 2801:8e:a000::/36 | No route object for it. A route object for 2801:8e::/32 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 2801:8e:804::/48 | No route object for it. A route object for 2801:8e::/32 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: none | 2801:8e:f000::/48 | No route object for it. A route object for 2801:8e::/32 with origin AS11993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11993 in the RIR database for the space. |
| Route object: RIR | 198.184.161.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS11993 whose prefix no peer sees AS11993 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 170.66.0.0/16 | RADB | Valid |
| 201.33.144.0/20 | RADB | Valid |
| 2801:8e::/32 | RADB | Valid |
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.