Network · data from 2026-11-12
AS274483 AS274483 - Locaweb Servicos de Internet S/A
Registry name: AS274483 - Locaweb Servicos de Internet S/A, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS274483, 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.
| 186.202.224.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 186.202.228.0/22 | Valid | Other IRR onlyRADB | 672 100% |
AS-SET
AS274483 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 62 are in fix.csv.
- Route object: RIR2
- Route object: not announced60
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 186.202.224.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.202.228.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS274483 whose prefix no peer sees AS274483 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 186.202.224.0/19 | RADB | Valid |
| 186.202.224.0/20 | RADB | Valid |
| 186.202.224.0/21 | RADB | Valid |
| 186.202.224.0/23 | RADB | Valid |
| 186.202.224.0/24 | RADB | Valid |
| 186.202.225.0/24 | RADB | Valid |
| 186.202.226.0/23 | RADB | Valid |
| 186.202.226.0/24 | RADB | Valid |
| 186.202.227.0/24 | RADB | Valid |
| 186.202.228.0/23 | RADB | Valid |
| 186.202.228.0/24 | RADB | Valid |
| 186.202.229.0/24 | RADB | Valid |
| 186.202.230.0/23 | RADB | Valid |
| 186.202.230.0/24 | RADB | Valid |
| 186.202.231.0/24 | RADB | Valid |
| 186.202.232.0/21 | RADB | Valid |
| 186.202.232.0/22 | RADB | Valid |
| 186.202.232.0/23 | RADB | Valid |
| 186.202.232.0/24 | RADB | Valid |
| 186.202.233.0/24 | RADB | Valid |
| 186.202.234.0/23 | RADB | Valid |
| 186.202.234.0/24 | RADB | Valid |
| 186.202.235.0/24 | RADB | Valid |
| 186.202.236.0/22 | RADB | Valid |
| 186.202.236.0/23 | RADB | Valid |
| 186.202.236.0/24 | RADB | Valid |
| 186.202.237.0/24 | RADB | Valid |
| 186.202.238.0/23 | RADB | Valid |
| 186.202.238.0/24 | RADB | Valid |
| 186.202.239.0/24 | RADB | Valid |
| 186.202.240.0/20 | RADB | Valid |
| 186.202.240.0/21 | RADB | Valid |
| 186.202.240.0/22 | RADB | Valid |
| 186.202.240.0/23 | RADB | Valid |
| 186.202.240.0/24 | RADB | Valid |
| 186.202.241.0/24 | RADB | Valid |
| 186.202.242.0/23 | RADB | Valid |
| 186.202.242.0/24 | RADB | Valid |
| 186.202.243.0/24 | RADB | Valid |
| 186.202.244.0/22 | RADB | Valid |
| 186.202.244.0/23 | RADB | Valid |
| 186.202.244.0/24 | RADB | Valid |
| 186.202.245.0/24 | RADB | Valid |
| 186.202.246.0/23 | RADB | Valid |
| 186.202.246.0/24 | RADB | Valid |
| 186.202.247.0/24 | RADB | Valid |
| 186.202.248.0/21 | RADB | Valid |
| 186.202.248.0/22 | RADB | Valid |
| 186.202.248.0/23 | RADB | Valid |
| 186.202.248.0/24 | RADB | Valid |
| 186.202.249.0/24 | RADB | Valid |
| 186.202.250.0/23 | RADB | Valid |
| 186.202.250.0/24 | RADB | Valid |
| 186.202.251.0/24 | RADB | Valid |
| 186.202.252.0/22 | RADB | Valid |
| 186.202.252.0/23 | RADB | Valid |
| 186.202.252.0/24 | RADB | Valid |
| 186.202.253.0/24 | RADB | Valid |
| 186.202.254.0/23 | RADB | Valid |
| 186.202.254.0/24 | 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.