Network · data from 2026-11-12
AS139138 GOPAY - Gopay Information Technology Co.,Ltd
Registry name: GOPAY - Gopay Information Technology Co.,Ltd, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS139138, 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.150.164.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.150.165.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 199.182.239.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 2406:b640:100::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2406:b640:4100::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 103.121.250.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
AS-SET
AS139138 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.150.164.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.150.165.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.182.239.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2406:b640:100::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2406:b640:4100::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS139138 whose prefix no peer sees AS139138 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.150.164.0/23 | APNIC | No ROA |
| 2406:b640::/32 | RADB | No ROA |
| 2406:b640::/40 | RADB | 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.