Network · data from 2026-11-12
AS58404 Qwords.com
Registry name: QWORDS-AS-ID - PT Qwords Company International, ID · PeeringDB
26IPv4 routes
100.0% RPKI valid · 84.6% with a route object
2IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
4 with no route object for this origin
7Low visibility
seen by under 10% of full-table peers
3Route objects not announced
registered with origin AS58404, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS58404, 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.
| 43.252.138.0/23 | Valid | Nonecovered by 43.252.136.0/22 | 3 0%low visibility |
| 103.102.152.0/23 | Valid | Nonecovered by 103.102.152.0/22 | 3 0%low visibility |
| 103.102.154.0/23 | Valid | Nonecovered by 103.102.152.0/22 | 3 0%low visibility |
| 103.195.90.0/23 | Valid | None | 3 0%low visibility |
| 103.28.13.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.28.14.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.28.15.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.195.89.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 103.195.90.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 103.195.91.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 103.28.12.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 2001:df0:2fc::/48 | Valid | Other IRR onlyNTTCOM | 635 100% |
| 43.252.136.0/23 | Valid | Other IRR onlyNTTCOM | 3 0%low visibility |
| 103.28.12.0/23 | Valid | Other IRR onlyNTTCOM | 3 0%low visibility |
| 103.28.14.0/23 | Valid | Other IRR onlyNTTCOM | 3 0%low visibility |
| 43.252.136.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 43.252.137.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 43.252.138.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 43.252.139.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.102.152.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 103.102.153.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 103.102.154.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 103.102.155.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 123.253.28.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 123.253.29.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 123.253.30.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 123.253.31.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 2001:df6:ac00::/48 | Valid | RIR databaseAPNIC | 635 100% |
AS-SET
AS58404'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 18 are in fix.csv.
- Route object: none4
- Route object: RIR11
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 43.252.138.0/23 | No route object for it. A route object for 43.252.136.0/22 with origin AS58404 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58404 in the RIR database for the space. |
| Route object: none | 103.102.152.0/23 | No route object for it. A route object for 103.102.152.0/22 with origin AS58404 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58404 in the RIR database for the space. |
| Route object: none | 103.102.154.0/23 | No route object for it. A route object for 103.102.152.0/22 with origin AS58404 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58404 in the RIR database for the space. |
| Route object: none | 103.195.90.0/23 | No route object for it. Add a route object with origin AS58404 in the RIR database for the space. |
| Route object: RIR | 103.28.13.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.28.14.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.28.15.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.195.89.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.195.90.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.195.91.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.28.12.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:df0:2fc::/48 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 43.252.136.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.28.12.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.28.14.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS58404 whose prefix no peer sees AS58404 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.252.136.0/22 | APNIC, NTTCOM | Valid |
| 103.28.12.0/22 | APNIC, NTTCOM | Valid |
| 103.102.152.0/22 | APNIC | 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.