Network · data from 2026-11-12
AS63567 PGYIDC - Suqian Pugongying Network Service Co.,Ltd
Registry name: PGYIDC - Suqian Pugongying Network Service Co.,Ltd, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS63567, 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.
| 103.205.252.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 669 99% |
| 103.239.244.0/23 | Valid | Other IRR onlyRADB | 669 99% |
| 103.40.12.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 668 99% |
| 111.223.12.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 668 99% |
| 43.248.184.0/21 | Valid | Other IRR onlyRADB | 659 98% |
AS-SET
AS63567 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 8 are in fix.csv.
- Route object: RIR5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.205.252.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.239.244.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.40.12.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.223.12.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.248.184.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS63567 whose prefix no peer sees AS63567 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.45.160.0/22 | APNIC, NTTCOM | Valid |
| 103.45.160.0/24 | NTTCOM | Valid |
| 103.239.244.0/22 | APNIC, NTTCOM | 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.