bgpreport

Network · data from 2026-11-12

AS131303 First Cagayan Converge Data Center, Inc

Registry name: FCCDCI-NET-PH - 4/F Podium RCBC Plaza Tower I, PH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS131303, 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.12.88.0/24 No ROA Other IRR onlyNTTCOM 671 100% 69
103.12.89.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 69
103.12.90.0/24 No ROA Other IRR onlyNTTCOM 671 100% 69
103.12.91.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 69
103.29.22.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 69
103.29.23.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 69
43.231.230.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
103.29.20.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
202.8.100.0/24 No ROA RIR databaseAPNIC 671 100% 69
202.8.102.0/24 No ROA RIR databaseAPNIC 671 100% 69
202.8.103.0/24 No ROA RIR databaseAPNIC 671 100% 69
43.231.228.0/24 No ROA RIR databaseAPNIC, NTTCOM 670 100% 69
103.29.21.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 670 100% 69

AS-SET

AS131303'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 52 are in fix.csv.

  • ROA: none13
  • Route object: RIR6
  • Route object: not announced33
ChangePrefix or setDetailFull-table peers
ROA: none103.12.88.0/24No ROA covers it. Add a ROA for AS131303, maxLength 24.671 of 673
Route object: RIR103.12.88.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none103.12.89.0/24No ROA covers it. Add a ROA for AS131303, maxLength 24.671 of 673
Route object: RIR103.12.89.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.12.90.0/24No ROA covers it. Add a ROA for AS131303, maxLength 24.671 of 673
Route object: RIR103.12.90.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none103.12.91.0/24No ROA covers it. Add a ROA for AS131303, maxLength 24.671 of 673
Route object: RIR103.12.91.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.29.22.0/24No ROA covers it. Add a ROA for AS131303, maxLength 24.671 of 673
Route object: RIR103.29.22.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.29.23.0/24No ROA covers it. Add a ROA for AS131303, maxLength 24.671 of 673
Route object: RIR103.29.23.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none43.231.230.0/24No ROA covers it. Add a ROA for AS131303, maxLength 24.671 of 673
ROA: none103.29.20.0/24No ROA covers it. Add a ROA for AS131303, maxLength 24.671 of 673
ROA: none202.8.100.0/24No ROA covers it. Add a ROA for AS131303, maxLength 24.671 of 673
ROA: none202.8.102.0/24No ROA covers it. Add a ROA for AS131303, maxLength 24.671 of 673
ROA: none202.8.103.0/24No ROA covers it. Add a ROA for AS131303, maxLength 24.671 of 673
ROA: none43.231.228.0/24No ROA covers it. Add a ROA for AS131303, maxLength 24.670 of 673
ROA: none103.29.21.0/24No ROA covers it. Add a ROA for AS131303, maxLength 24.670 of 673

Route objects not announced

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

43.231.228.0/22APNIC, NTTCOM, RADBNo ROA
43.231.228.0/23APNIC, NTTCOM, RADBNo ROA
43.231.229.0/24NTTCOM, RADBNo ROA
43.231.230.0/23APNIC, NTTCOM, RADBNo ROA
43.231.231.0/24APNIC, NTTCOM, RADBNo ROA
103.12.88.0/22NTTCOM, RADBNo ROA
103.12.88.0/23NTTCOMNo ROA
103.12.90.0/23NTTCOM, RADBNo ROA
103.29.20.0/22NTTCOM, RADBNo ROA
103.29.20.0/23NTTCOM, RADBNo ROA
103.29.22.0/23NTTCOM, RADBNo ROA
103.79.212.0/24NTTCOM, RADBNo ROA
202.8.100.0/22APNICNo ROA
202.8.100.0/23APNICNo ROA
202.8.101.0/24APNICNo ROA
202.8.102.0/23APNICNo ROA
2405:3940::/32APNICNo ROA
2405:3940::/40APNICNo ROA
2405:3940:100::/40APNICNo ROA
2405:3940:200::/40APNICNo ROA
2405:3940:300::/40APNICNo ROA
2405:3940:400::/40APNICNo ROA
2405:3940:500::/40APNICNo ROA
2405:3940:600::/40APNICNo ROA
2405:3940:700::/40APNICNo ROA
2405:3940:800::/40APNICNo ROA
2405:3940:900::/40APNICNo ROA
2405:3940:a00::/40APNICNo ROA
2405:3940:b00::/40APNICNo ROA
2405:3940:c00::/40APNICNo ROA
2405:3940:d00::/40APNICNo ROA
2405:3940:e00::/40APNICNo ROA
2405:3940:f00::/40APNICNo 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.