Network · data from 2026-11-12
AS152611 Beidou LTD
Registry name: BEIDOU - Beidou LTD, TW · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS152611, 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.
| 151.242.53.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 103.23.108.0/23 | Valid | RIR databaseAPNIC | 670 100% |
| 160.30.78.0/24 | Valid | RIR databaseAPNIC, RADB | 667 99% |
| 160.30.79.0/24 | Valid | RIR databaseAPNIC, RADB | 667 99% |
| 103.23.109.0/24 | Valid | RIR databaseAPNIC | 198 29% |
AS-SET
AS152611'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 4 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 151.242.53.0/24 | ROAs covering it name AS834, not AS152611. If AS152611 should announce it, add a ROA for AS152611. |
| Route object: none | 151.242.53.0/24 | Route objects for it name AS834. Add a route object with origin AS152611 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS152611 whose prefix no peer sees AS152611 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.23.108.0/24 | APNIC | Valid |
| 160.30.78.0/23 | APNIC, 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.