bgpreport

Network · data from 2026-11-12

AS131588 FISC-AS-TW - Financial Information Service Co., Ltd.

Registry name: FISC-AS-TW - Financial Information Service Co., Ltd., TW · not in PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 routes 100.0% RPKI valid · 80.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS131588, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS131588, 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.

2400:e480::/48 Valid Nonecovered by 2400:e480::/32 636 100% 67
103.229.132.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 66
103.229.134.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
103.229.135.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
2400:e480::/32 Valid Other IRR onlyRADB 635 100% 70
2400:e480:1::/48 Valid Other IRR onlyRADB 635 100% 70
2400:e480:2::/48 Valid Other IRR onlyRADB 635 100% 70
2400:e480:d::/48 Valid Other IRR onlyRADB 635 100% 67

AS-SET

AS131588 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 12 are in fix.csv.

  • Route object: none1
  • Route object: RIR7
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none2400:e480::/48No route object for it. A route object for 2400:e480::/32 with origin AS131588 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131588 in the RIR database for the space.636 of 636
Route object: RIR103.229.132.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.229.134.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.229.135.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2400:e480::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2400:e480:1::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2400:e480:2::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2400:e480:d::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

103.229.132.0/22NTTCOM, RADBNo ROA
103.229.132.0/23NTTCOM, RADBNo ROA
103.229.133.0/24NTTCOM, RADBNo ROA
103.229.134.0/23NTTCOM, RADBNo 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.