Network · data from 2026-11-12
AS52250 ADSIB
Registry name: AS52250 - Ag para el Desarrollo de la Sociedad de la Inf en Bolivia - ADSIB, BO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52250, 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.
| 166.114.2.0/24 | Valid | Nonecovered by 166.114.0.0/16 | 669 99% |
| 200.9.168.0/24 | Valid | Other IRR onlyALTDB, RADB | 671 100% |
| 166.114.1.0/24 | Valid | Other IRR onlyALTDB | 670 100% |
AS-SET
AS52250's PeeringDB record names no 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 9 are in fix.csv.
- Route object: none1
- Route object: RIR2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 166.114.2.0/24 | No route object for it. A route object for 166.114.0.0/16 with origin AS52250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52250 in the RIR database for the space. |
| Route object: RIR | 200.9.168.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 166.114.1.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52250 whose prefix no peer sees AS52250 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 166.114.0.0/16 | ALTDB | No ROA |
| 200.9.165.0/24 | ALTDB | Valid |
| 200.9.166.0/23 | ALTDB | Valid |
| 200.9.166.0/24 | ALTDB | Valid |
| 200.9.167.0/24 | ALTDB | Valid |
| 2001:1378::/32 | 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.