bgpreport

Network · data from 2026-11-12

AS137904 BVPL-AS-AP - Black & Veatch (SEA) PTE LTD

Registry name: BVPL-AS-AP - Black & Veatch (SEA) PTE LTD, SG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS137904, 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.
147.182.64.0/21 No ROA Nonecovered by 147.182.0.0/17 673 100% 67
147.182.72.0/22 No ROA Nonecovered by 147.182.0.0/17 671 100% 67
147.182.78.0/24 No ROA Nonecovered by 147.182.0.0/17 671 100% 67
147.182.79.0/24 No ROA Nonecovered by 147.182.0.0/17 671 100% 67
147.182.76.0/24 No ROA Other IRR onlyNTTCOM 671 100% 67

AS-SET

AS137904 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 11 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none147.182.64.0/21No ROA covers it. Add a ROA for AS137904, maxLength 21.673 of 673
Route object: none147.182.64.0/21No route object for it. A route object for 147.182.0.0/17 with origin AS137904 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137904 in the RIR database for the space.673 of 673
ROA: none147.182.72.0/22No ROA covers it. Add a ROA for AS137904, maxLength 22.671 of 673
Route object: none147.182.72.0/22No route object for it. A route object for 147.182.0.0/17 with origin AS137904 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137904 in the RIR database for the space.671 of 673
ROA: none147.182.78.0/24No ROA covers it. Add a ROA for AS137904, maxLength 24.671 of 673
Route object: none147.182.78.0/24No route object for it. A route object for 147.182.0.0/17 with origin AS137904 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137904 in the RIR database for the space.671 of 673
ROA: none147.182.79.0/24No ROA covers it. Add a ROA for AS137904, maxLength 24.671 of 673
Route object: none147.182.79.0/24No route object for it. A route object for 147.182.0.0/17 with origin AS137904 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137904 in the RIR database for the space.671 of 673
ROA: none147.182.76.0/24No ROA covers it. Add a ROA for AS137904, maxLength 24.671 of 673
Route object: RIR147.182.76.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

147.182.0.0/17NTTCOMNo 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.