Network · data from 2026-11-12
AS131285 Blueberry Telecom Global Pte Ltd
Registry name: CHINATELECOM-HUBEI-SHENGJI-5G-NETWORK - CHINATELECOM Hubei province Shengji 5G network, CN · PeeringDB
12IPv4 routes
100.0% RPKI valid · 100.0% with a route object
26IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
5Route objects not announced
registered with origin AS131285, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS131285, 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.
| 111.181.0.0/16 | Valid | Other IRR onlyRADB | 672 100% |
| 111.181.0.0/17 | Valid | Other IRR onlyRADB | 672 100% |
| 111.181.128.0/17 | Valid | Other IRR onlyRADB | 672 100% |
| 111.181.160.0/19 | Valid | Other IRR onlyRADB | 672 100% |
| 111.181.222.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 111.181.224.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 111.183.0.0/16 | Valid | Other IRR onlyRADB | 672 100% |
| 111.183.0.0/17 | Valid | Other IRR onlyRADB | 672 100% |
| 111.183.128.0/17 | Valid | Other IRR onlyRADB | 672 100% |
| 111.183.160.0/19 | Valid | Other IRR onlyRADB | 672 100% |
| 111.183.222.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 111.183.224.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 240e:25d::/36 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:25d::/37 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:25d:800::/37 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:45c::/32 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:45c::/33 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:45c:8000::/33 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:45d::/32 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:45d::/33 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:45d:8000::/33 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85c::/44 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85c::/45 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85c:8::/45 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85c:10::/47 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85c:40::/44 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85c:40::/45 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85c:48::/45 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85c:50::/47 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85c:80::/47 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85c:82::/47 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85d::/44 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85d::/45 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85d:8::/45 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85d:10::/44 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85d:10::/45 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:85d:18::/45 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:45f:fffc::/46 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
AS131285'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 43 are in fix.csv.
- Route object: RIR38
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 111.181.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.181.0.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.181.128.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.181.160.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.181.222.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.181.224.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.183.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.183.0.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.183.128.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.183.160.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.183.222.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.183.224.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:25d::/36 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:25d::/37 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:25d:800::/37 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:45c::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:45c::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:45c:8000::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:45d::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:45d::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:45d:8000::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85c::/44 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85c::/45 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85c:8::/45 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85c:10::/47 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85c:40::/44 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85c:40::/45 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85c:48::/45 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85c:50::/47 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85c:80::/47 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85c:82::/47 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85d::/44 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85d::/45 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85d:8::/45 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85d:10::/44 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85d:10::/45 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:85d:18::/45 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:45f:fffc::/46 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS131285 whose prefix no peer sees AS131285 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 111.181.222.0/24 | RADB | Valid |
| 111.181.223.0/24 | RADB | Valid |
| 111.183.222.0/24 | RADB | Valid |
| 111.183.223.0/24 | RADB | Valid |
| 202.47.89.0/24 | NTTCOM | No ROA |
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.