bgpreport

Network · data from 2026-11-12

AS18396 PHILCOMCORP-MND-AS-AP - PLDT-PhilCom Inc.

Registry name: PHILCOMCORP-MND-AS-AP - PLDT-PhilCom Inc., PH · not in PeeringDB

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

Announced routes

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

122.144.112.0/22 No ROA Nonecovered by 122.144.64.0/18 65 10%low visibility 25
122.144.64.0/24 No ROA Nonecovered by 122.144.64.0/18 63 9%low visibility 24
122.144.65.0/24 No ROA Nonecovered by 122.144.64.0/18 63 9%low visibility 24
122.144.67.0/24 No ROA Nonecovered by 122.144.64.0/18 63 9%low visibility 24
122.144.68.0/24 No ROA Nonecovered by 122.144.64.0/18 63 9%low visibility 24
122.144.69.0/24 No ROA Nonecovered by 122.144.64.0/18 63 9%low visibility 24
122.144.70.0/24 No ROA Nonecovered by 122.144.64.0/18 63 9%low visibility 24
122.144.71.0/24 No ROA Nonecovered by 122.144.64.0/18 63 9%low visibility 24
202.84.119.0/24 No ROA Nonecovered by 202.84.116.0/22 62 9%low visibility 24
202.84.124.0/24 No ROA Nonecovered by 202.84.96.0/19 62 9%low visibility 24
202.84.127.0/24 No ROA Nonecovered by 202.84.96.0/19 62 9%low visibility 24
202.84.106.0/24 No ROA Nonecovered by 202.84.106.0/23 59 9%low visibility 23
122.144.116.0/22 No ROA Other IRR onlyRADB 61 9%low visibility 24
202.84.104.0/24 No ROA Other IRR onlyRADB 59 9%low visibility 23
202.84.114.0/24 No ROA Other IRR onlyNTTCOM 59 9%low visibility 23
202.84.115.0/24 No ROA Other IRR onlyNTTCOM 59 9%low visibility 23
202.84.125.0/24 No ROA Other IRR onlyNTTCOM, RADB 59 9%low visibility 23
202.84.96.0/23 No ROA Other IRR onlyNTTCOM, RADB 58 9%low visibility 23
202.84.107.0/24 No ROA Other IRR onlyRADB 58 9%low visibility 23
202.84.111.0/24 No ROA Other IRR onlyNTTCOM 58 9%low visibility 23
202.84.113.0/24 No ROA Other IRR onlyRADB 58 9%low visibility 23

AS-SET

AS18396 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 67 are in fix.csv.

  • ROA: none21
  • Route object: none12
  • Route object: RIR9
  • Route object: not announced25
ChangePrefix or setDetailFull-table peers
ROA: none122.144.112.0/22No ROA covers it. Add a ROA for AS18396, maxLength 22.65 of 673
Route object: none122.144.112.0/22No route object for it. A route object for 122.144.64.0/18 with origin AS18396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18396 in the RIR database for the space.65 of 673
ROA: none122.144.64.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.63 of 673
Route object: none122.144.64.0/24No route object for it. A route object for 122.144.64.0/18 with origin AS18396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18396 in the RIR database for the space.63 of 673
ROA: none122.144.65.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.63 of 673
Route object: none122.144.65.0/24No route object for it. A route object for 122.144.64.0/18 with origin AS18396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18396 in the RIR database for the space.63 of 673
ROA: none122.144.67.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.63 of 673
Route object: none122.144.67.0/24No route object for it. A route object for 122.144.64.0/18 with origin AS18396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18396 in the RIR database for the space.63 of 673
ROA: none122.144.68.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.63 of 673
Route object: none122.144.68.0/24No route object for it. A route object for 122.144.64.0/18 with origin AS18396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18396 in the RIR database for the space.63 of 673
ROA: none122.144.69.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.63 of 673
Route object: none122.144.69.0/24No route object for it. A route object for 122.144.64.0/18 with origin AS18396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18396 in the RIR database for the space.63 of 673
ROA: none122.144.70.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.63 of 673
Route object: none122.144.70.0/24No route object for it. A route object for 122.144.64.0/18 with origin AS18396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18396 in the RIR database for the space.63 of 673
ROA: none122.144.71.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.63 of 673
Route object: none122.144.71.0/24No route object for it. A route object for 122.144.64.0/18 with origin AS18396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18396 in the RIR database for the space.63 of 673
ROA: none202.84.119.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.62 of 673
Route object: none202.84.119.0/24No route object for it. A route object for 202.84.116.0/22 with origin AS18396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18396 in the RIR database for the space.62 of 673
ROA: none202.84.124.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.62 of 673
Route object: none202.84.124.0/24No route object for it. A route object for 202.84.96.0/19 with origin AS18396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18396 in the RIR database for the space.62 of 673
ROA: none202.84.127.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.62 of 673
Route object: none202.84.127.0/24No route object for it. A route object for 202.84.96.0/19 with origin AS18396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18396 in the RIR database for the space.62 of 673
ROA: none202.84.106.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.59 of 673
Route object: none202.84.106.0/24No route object for it. A route object for 202.84.106.0/23 with origin AS18396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18396 in the RIR database for the space.59 of 673
ROA: none122.144.116.0/22No ROA covers it. Add a ROA for AS18396, maxLength 22.61 of 673
Route object: RIR122.144.116.0/22Route object only in RADB. Add it in the RIR database for the space.61 of 673
ROA: none202.84.104.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.59 of 673
Route object: RIR202.84.104.0/24Route object only in RADB. Add it in the RIR database for the space.59 of 673
ROA: none202.84.114.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.59 of 673
Route object: RIR202.84.114.0/24Route object only in NTTCOM. Add it in the RIR database for the space.59 of 673
ROA: none202.84.115.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.59 of 673
Route object: RIR202.84.115.0/24Route object only in NTTCOM. Add it in the RIR database for the space.59 of 673
ROA: none202.84.125.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.59 of 673
Route object: RIR202.84.125.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.59 of 673
ROA: none202.84.96.0/23No ROA covers it. Add a ROA for AS18396, maxLength 23.58 of 673
Route object: RIR202.84.96.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.58 of 673
ROA: none202.84.107.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.58 of 673
Route object: RIR202.84.107.0/24Route object only in RADB. Add it in the RIR database for the space.58 of 673
ROA: none202.84.111.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.58 of 673
Route object: RIR202.84.111.0/24Route object only in NTTCOM. Add it in the RIR database for the space.58 of 673
ROA: none202.84.113.0/24No ROA covers it. Add a ROA for AS18396, maxLength 24.58 of 673
Route object: RIR202.84.113.0/24Route object only in RADB. Add it in the RIR database for the space.58 of 673

Route objects not announced

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

122.144.64.0/18NTTCOM, RADBNo ROA
122.144.96.0/20RADBNo ROA
202.84.96.0/19NTTCOM, RADBNo ROA
202.84.96.0/20NTTCOMNo ROA
202.84.98.0/24RADBNo ROA
202.84.99.0/24NTTCOM, RADBNo ROA
202.84.100.0/24NTTCOM, RADBNo ROA
202.84.101.0/24NTTCOM, RADBNo ROA
202.84.102.0/23RADBNo ROA
202.84.105.0/24RADBNo ROA
202.84.106.0/23RADBNo ROA
202.84.108.0/24RADBNo ROA
202.84.109.0/24NTTCOM, RADBNo ROA
202.84.110.0/23RADBNo ROA
202.84.110.0/24NTTCOMNo ROA
202.84.112.0/24RADBNo ROA
202.84.114.0/23RADBNo ROA
202.84.116.0/22NTTCOM, RADBNo ROA
202.84.116.0/24RADBNo ROA
202.84.117.0/24RADBNo ROA
202.84.118.0/24RADBNo ROA
202.84.120.0/22RADBNo ROA
202.84.122.0/24RADBNo ROA
202.84.123.0/24RADBNo ROA
202.84.126.0/24RADBNo 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.