Network · data from 2026-11-12
AS61945 AS61945 - PIX BRASIL NETWORKS LTDA
Registry name: AS61945 - PIX BRASIL NETWORKS LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61945, 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.
| 168.222.100.0/24 | Valid | Nonecovered by 168.222.100.0/22 | 671 100% |
| 168.222.101.0/24 | Valid | Nonecovered by 168.222.100.0/22 | 671 100% |
| 168.222.102.0/24 | Valid | Nonecovered by 168.222.100.0/22 | 671 100% |
| 168.222.103.0/24 | Valid | Nonecovered by 168.222.100.0/22 | 671 100% |
| 2804:18a4::/32 | Valid | Other IRR onlyRADB | 632 99% |
AS-SET
AS61945 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 15 are in fix.csv.
- Route object: none4
- Route object: RIR1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 168.222.100.0/24 | No route object for it. A route object for 168.222.100.0/22 with origin AS61945 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61945 in the RIR database for the space. |
| Route object: none | 168.222.101.0/24 | No route object for it. A route object for 168.222.100.0/22 with origin AS61945 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61945 in the RIR database for the space. |
| Route object: none | 168.222.102.0/24 | No route object for it. A route object for 168.222.100.0/22 with origin AS61945 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61945 in the RIR database for the space. |
| Route object: none | 168.222.103.0/24 | No route object for it. A route object for 168.222.100.0/22 with origin AS61945 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61945 in the RIR database for the space. |
| Route object: RIR | 2804:18a4::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61945 whose prefix no peer sees AS61945 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.222.100.0/22 | RADB, RIPE | Valid |
| 187.86.20.0/22 | RADB | No ROA |
| 192.140.37.0/24 | RADB | No ROA |
| 192.140.38.0/23 | RADB | No ROA |
| 201.159.88.0/21 | RADB | No ROA |
| 201.159.88.0/22 | RADB | No ROA |
| 201.159.90.0/23 | RADB | No ROA |
| 201.159.90.0/24 | RADB | No ROA |
| 201.159.93.0/24 | RADB | No ROA |
| 201.159.95.0/24 | 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.