Network · data from 2026-11-12
AS52866
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52866, 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.125.24.0/22 | Valid | Other IRR onlyRADB, TC | 0 0%low visibility |
| 177.125.24.0/23 | Valid | Other IRR onlyRADB | 0 0%low visibility |
| 177.125.26.0/23 | Valid | Other IRR onlyRADB | 0 0%low visibility |
AS-SET
AS52866 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 41 are in fix.csv.
- Route object: RIR3
- Route object: not announced38
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 177.125.24.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.125.24.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.125.26.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52866 whose prefix no peer sees AS52866 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.100.128.0/23 | RADB | Valid |
| 131.100.128.0/24 | RADB | Valid |
| 131.100.129.0/24 | RADB | Valid |
| 131.100.130.0/23 | RADB | Valid |
| 131.100.130.0/24 | RADB | Valid |
| 131.100.131.0/24 | RADB | Valid |
| 138.94.112.0/22 | RADB | Valid |
| 138.94.112.0/23 | RADB | Valid |
| 138.94.112.0/24 | RADB | Valid |
| 138.94.113.0/24 | RADB | Valid |
| 138.94.114.0/23 | RADB | Valid |
| 138.94.114.0/24 | RADB | Valid |
| 138.94.115.0/24 | RADB | Valid |
| 170.81.244.0/22 | RADB | Valid |
| 170.81.244.0/23 | RADB | Valid |
| 170.81.244.0/24 | RADB | Valid |
| 170.81.245.0/24 | RADB | Valid |
| 170.81.246.0/23 | RADB | Valid |
| 170.81.246.0/24 | RADB | Valid |
| 170.81.247.0/24 | RADB | Valid |
| 177.125.24.0/24 | RADB, TC | Valid |
| 177.125.25.0/24 | RADB, TC | Valid |
| 177.125.26.0/24 | RADB, TC | Valid |
| 177.125.27.0/24 | RADB, TC | Valid |
| 186.233.220.0/22 | RADB | Valid |
| 186.233.220.0/23 | RADB | Valid |
| 186.233.220.0/24 | RADB | Valid |
| 186.233.221.0/24 | RADB | Valid |
| 186.233.222.0/23 | RADB | Valid |
| 186.233.222.0/24 | RADB | Valid |
| 186.233.223.0/24 | RADB | Valid |
| 2804:bdc::/32 | RADB | Valid |
| 2804:bdc::/33 | RADB | Valid |
| 2804:bdc::/34 | RADB | Valid |
| 2804:bdc:4000::/34 | RADB | Valid |
| 2804:bdc:8000::/33 | RADB | Valid |
| 2804:bdc:8000::/34 | RADB | Valid |
| 2804:bdc:c000::/34 | 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.