bgpreport

Network · data from 2026-11-12

AS131418 SHOPEEPAY-VN - SHOPEEPAY JOINT STOCK COMPANY

Registry name: SHOPEEPAY-VN - SHOPEEPAY JOINT STOCK COMPANY, VN · not in PeeringDB

11IPv4 routes 45.5% RPKI valid · 81.8% with a route object
3IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No ROA 2 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS131418, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS131418, 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.78.84.0/22 No ROA Other origin only 670 100% 67
103.117.244.0/24 No ROA Other origin only 670 100% 67
45.119.240.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
45.119.241.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
2001:df3:8600::/48 No ROA Other IRR onlyRADB 635 100% 69
2001:df5:b700::/48 No ROA Other IRR onlyRADB 635 100% 69
2001:df5:b900::/48 No ROA Other IRR onlyRADB 635 100% 69
45.119.240.0/22 No ROA Other IRR onlyNTTCOM, RADB 149 22% 37
45.119.242.0/24 No ROA Other IRR onlyNTTCOM 59 9%low visibility 29
103.239.120.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.239.121.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.239.122.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
45.119.243.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
103.239.120.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67

AS-SET

AS131418 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 26 are in fix.csv.

  • ROA: none9
  • Route object: none2
  • Route object: RIR7
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none103.78.84.0/22No ROA covers it. Add a ROA for AS131418, maxLength 22.670 of 673
Route object: none103.78.84.0/22Route objects for it name AS63767. Add a route object with origin AS131418 in the RIR database for the space.670 of 673
ROA: none103.117.244.0/24No ROA covers it. Add a ROA for AS131418, maxLength 24.670 of 673
Route object: none103.117.244.0/24Route objects for it name AS135948. Add a route object with origin AS131418 in the RIR database for the space.670 of 673
ROA: none45.119.240.0/24No ROA covers it. Add a ROA for AS131418, maxLength 24.672 of 673
Route object: RIR45.119.240.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.119.241.0/24No ROA covers it. Add a ROA for AS131418, maxLength 24.672 of 673
Route object: RIR45.119.241.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none2001:df3:8600::/48No ROA covers it. Add a ROA for AS131418, maxLength 48.635 of 636
Route object: RIR2001:df3:8600::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2001:df5:b700::/48No ROA covers it. Add a ROA for AS131418, maxLength 48.635 of 636
Route object: RIR2001:df5:b700::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2001:df5:b900::/48No ROA covers it. Add a ROA for AS131418, maxLength 48.635 of 636
Route object: RIR2001:df5:b900::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none45.119.240.0/22No ROA covers it. Add a ROA for AS131418, maxLength 22.149 of 673
Route object: RIR45.119.240.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.149 of 673
ROA: none45.119.242.0/24No ROA covers it. Add a ROA for AS131418, maxLength 24.59 of 673
Route object: RIR45.119.242.0/24Route object only in NTTCOM. Add it in the RIR database for the space.59 of 673

Route objects not announced

Route objects with origin AS131418 whose prefix no peer sees AS131418 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.239.120.0/23APNIC, NTTCOM, RADBValid
103.239.122.0/23APNIC, NTTCOM, RADBValid
103.239.123.0/24APNIC, NTTCOM, RADBValid
2001:df3:8a00::/48NTTCOMNo ROA
2001:df3:8a00::/50NTTCOMNo ROA
2001:df3:8a00:4000::/50NTTCOMNo ROA
2001:df3:8a00:8000::/50NTTCOMNo ROA
2001:df3:8a00:c000::/50NTTCOMNo 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.