Network · data from 2026-11-12
AS38843 PUMO-NET - PUMO NETWORK DIGITAL TECHNOLOGY CO.,LTD
Registry name: PUMO-NET - PUMO NETWORK DIGITAL TECHNOLOGY CO.,LTD, TW · not in PeeringDB
16IPv4 routes
100.0% RPKI valid · 100.0% with a route object
1IPv6 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
43Route objects not announced
registered with origin AS38843, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS38843, 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.20.40.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 124.150.128.0/21 | Valid | Other IRR onlyRADB | 673 100% |
| 124.150.128.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 223.27.32.0/19 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 223.27.32.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 223.27.33.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 223.27.40.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 223.27.48.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 223.27.59.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 223.27.61.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 124.150.128.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 124.150.132.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 223.27.34.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 223.27.43.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 223.27.48.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 223.27.52.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 2400:b380::/32 | Valid | Other IRR onlyRADB | 636 100% |
AS-SET
AS38843 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 60 are in fix.csv.
- Route object: RIR17
- Route object: not announced43
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.20.40.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.150.128.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.150.128.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.27.32.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.27.32.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.27.33.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.27.40.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.27.48.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.27.59.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.27.61.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.150.128.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.150.132.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.27.34.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.27.43.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.27.48.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.27.52.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:b380::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38843 whose prefix no peer sees AS38843 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.20.40.0/23 | NTTCOM | Valid |
| 103.20.40.0/24 | NTTCOM, RADB | Valid |
| 103.20.41.0/24 | NTTCOM, RADB | Valid |
| 103.20.42.0/23 | NTTCOM | Valid |
| 103.20.42.0/24 | NTTCOM, RADB | Valid |
| 103.20.43.0/24 | NTTCOM, RADB | Valid |
| 124.150.129.0/24 | NTTCOM, RADB | Valid |
| 124.150.130.0/24 | NTTCOM, RADB | Valid |
| 124.150.131.0/24 | NTTCOM, RADB | Valid |
| 124.150.132.0/24 | NTTCOM, RADB | Valid |
| 124.150.133.0/24 | NTTCOM, RADB | Valid |
| 124.150.134.0/24 | RADB | Valid |
| 124.150.135.0/24 | NTTCOM, RADB | Valid |
| 223.27.32.0/21 | RADB | Valid |
| 223.27.32.0/24 | RADB | Valid |
| 223.27.35.0/24 | RADB | Valid |
| 223.27.36.0/24 | RADB | Valid |
| 223.27.37.0/24 | RADB | Valid |
| 223.27.38.0/24 | RADB | Valid |
| 223.27.39.0/24 | RADB | Valid |
| 223.27.40.0/21 | RADB | Valid |
| 223.27.41.0/24 | RADB | Valid |
| 223.27.42.0/24 | RADB | Valid |
| 223.27.44.0/24 | RADB | Valid |
| 223.27.45.0/24 | RADB | Valid |
| 223.27.46.0/24 | RADB | Valid |
| 223.27.47.0/24 | RADB | Valid |
| 223.27.48.0/21 | RADB | Valid |
| 223.27.49.0/24 | RADB | Valid |
| 223.27.50.0/24 | RADB | Valid |
| 223.27.51.0/24 | RADB | Valid |
| 223.27.53.0/24 | RADB | Valid |
| 223.27.54.0/24 | RADB | Valid |
| 223.27.55.0/24 | RADB | Valid |
| 223.27.56.0/21 | RADB | Valid |
| 223.27.56.0/22 | RADB | Valid |
| 223.27.56.0/24 | RADB | Valid |
| 223.27.57.0/24 | RADB | Valid |
| 223.27.58.0/24 | RADB | Valid |
| 223.27.60.0/22 | RADB | Valid |
| 223.27.60.0/24 | RADB | Valid |
| 223.27.62.0/24 | RADB | Valid |
| 223.27.63.0/24 | 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.