Network · data from 2026-11-12
AS52933 AS52933 - CONECTIVA TECNOLOGIA LTDA
Registry name: AS52933 - CONECTIVA TECNOLOGIA LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52933, 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.10.180.0/24 | Valid | Nonecovered by 177.10.180.0/22 | 672 100% |
| 177.10.181.0/24 | Valid | Nonecovered by 177.10.180.0/22 | 672 100% |
| 177.10.183.0/24 | Valid | Nonecovered by 177.10.180.0/22 | 671 100% |
| 177.10.182.0/24 | Valid | Nonecovered by 177.10.180.0/22 | 670 100% |
| 2804:b00:c000::/34 | Valid | Nonecovered by 2804:b00::/32 | 636 100% |
| 2804:b00:4000::/34 | Valid | Nonecovered by 2804:b00::/32 | 634 100% |
| 177.10.180.0/22 | Valid | Other IRR onlyRADB | 672 100% |
AS-SET
AS52933 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 8 are in fix.csv.
- Route object: none6
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 177.10.180.0/24 | No route object for it. A route object for 177.10.180.0/22 with origin AS52933 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52933 in the RIR database for the space. |
| Route object: none | 177.10.181.0/24 | No route object for it. A route object for 177.10.180.0/22 with origin AS52933 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52933 in the RIR database for the space. |
| Route object: none | 177.10.183.0/24 | No route object for it. A route object for 177.10.180.0/22 with origin AS52933 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52933 in the RIR database for the space. |
| Route object: none | 177.10.182.0/24 | No route object for it. A route object for 177.10.180.0/22 with origin AS52933 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52933 in the RIR database for the space. |
| Route object: none | 2804:b00:c000::/34 | No route object for it. A route object for 2804:b00::/32 with origin AS52933 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52933 in the RIR database for the space. |
| Route object: none | 2804:b00:4000::/34 | No route object for it. A route object for 2804:b00::/32 with origin AS52933 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52933 in the RIR database for the space. |
| Route object: RIR | 177.10.180.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52933 whose prefix no peer sees AS52933 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:b00::/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.