Network · data from 2026-11-12
AS263108 AS263108 - OPANET TELECOMUNICACOES LTDA - ME
Registry name: AS263108 - OPANET TELECOMUNICACOES LTDA - ME, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263108, 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.92.128.0/22 | Valid | Nonecovered by 177.92.128.0/21 | 671 100% |
| 177.92.130.0/23 | Valid | Nonecovered by 177.92.128.0/21 | 671 100% |
| 177.92.132.0/22 | Valid | Nonecovered by 177.92.128.0/21 | 671 100% |
| 177.92.132.0/23 | Valid | Nonecovered by 177.92.128.0/21 | 671 100% |
| 177.92.134.0/23 | Valid | Nonecovered by 177.92.128.0/21 | 671 100% |
| 177.92.128.0/23 | Valid | Nonecovered by 177.92.128.0/21 | 669 99% |
| 177.92.128.0/21 | Valid | Other IRR onlyALTDB, RADB | 671 100% |
| 2804:16ec::/32 | Valid | Other IRR onlyALTDB, RADB | 633 100% |
AS-SET
AS263108 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 14 are in fix.csv.
- Route object: none6
- Route object: RIR2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 177.92.128.0/22 | No route object for it. A route object for 177.92.128.0/21 with origin AS263108 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263108 in the RIR database for the space. |
| Route object: none | 177.92.130.0/23 | No route object for it. A route object for 177.92.128.0/21 with origin AS263108 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263108 in the RIR database for the space. |
| Route object: none | 177.92.132.0/22 | No route object for it. A route object for 177.92.128.0/21 with origin AS263108 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263108 in the RIR database for the space. |
| Route object: none | 177.92.132.0/23 | No route object for it. A route object for 177.92.128.0/21 with origin AS263108 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263108 in the RIR database for the space. |
| Route object: none | 177.92.134.0/23 | No route object for it. A route object for 177.92.128.0/21 with origin AS263108 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263108 in the RIR database for the space. |
| Route object: none | 177.92.128.0/23 | No route object for it. A route object for 177.92.128.0/21 with origin AS263108 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263108 in the RIR database for the space. |
| Route object: RIR | 177.92.128.0/21 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:16ec::/32 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263108 whose prefix no peer sees AS263108 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.92.128.0/24 | ALTDB | Valid |
| 177.92.129.0/24 | ALTDB, RADB | Valid |
| 177.92.132.0/24 | RADB | Valid |
| 177.92.133.0/24 | RADB | Valid |
| 177.92.134.0/24 | RADB | Valid |
| 177.92.135.0/24 | ALTDB, 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.