bgpreport

Network · data from 2026-11-12

AS152475 BGPNETPTELTD-AS-AP - BGPNET PTE. LTD.

Registry name: BGPNETPTELTD-AS-AP - BGPNET PTE. LTD., SG · not in PeeringDB

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

Announced routes

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

79.109.228.0/24 Invalid: origin Other origin only 2 0%low visibility 2
79.109.229.0/24 Invalid: origin Other origin only 2 0%low visibility 2
79.109.230.0/24 Invalid: origin Other origin only 2 0%low visibility 2
79.109.231.0/24 Invalid: origin Other origin only 2 0%low visibility 2
160.30.129.129/32 Invalid: maxLength Nonecovered by 160.30.129.0/24 0 0%low visibility 1
148.178.127.0/24 No ROA Other IRR onlyRADB 667 99% 67
199.165.238.0/24 No ROA Other IRR onlyRADB 663 99% 67
103.152.247.0/24 Valid Other IRR onlyRADB 670 100% 67
103.136.33.0/24 Valid RIR databaseAPNIC 672 100% 67
103.136.35.0/24 Valid RIR databaseAPNIC 672 100% 67
103.96.1.0/24 Valid RIR databaseAPNIC 671 100% 67
79.109.6.0/24 Valid RIR databaseAPNIC 670 100% 67
103.129.52.0/24 Valid RIR databaseAPNIC 670 100% 67
160.30.129.0/24 Valid RIR databaseAPNIC 670 100% 67
160.30.128.0/24 Valid RIR databaseAPNIC 669 99% 67
103.129.53.0/24 Valid RIR databaseAPNIC 668 99% 67
2401:bbe0::/40 Valid RIR databaseAPNIC 636 100% 67
2401:bbe0:300::/40 Valid RIR databaseAPNIC 636 100% 68
2401:bbe0:100::/40 Valid RIR databaseAPNIC 635 100% 67

AS-SET

AS152475 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 24 are in fix.csv.

  • ROA: origin4
  • ROA: maxLength1
  • ROA: none2
  • Route object: none5
  • Route object: RIR3
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: origin79.109.228.0/24ROAs covering it name AS137551, not AS152475. If AS152475 should announce it, add a ROA for AS152475.2 of 673
Route object: none79.109.228.0/24Route objects for it name AS137551. Add a route object with origin AS152475 in the RIR database for the space.2 of 673
ROA: origin79.109.229.0/24ROAs covering it name AS137551, not AS152475. If AS152475 should announce it, add a ROA for AS152475.2 of 673
Route object: none79.109.229.0/24Route objects for it name AS137551. Add a route object with origin AS152475 in the RIR database for the space.2 of 673
ROA: origin79.109.230.0/24ROAs covering it name AS137551, not AS152475. If AS152475 should announce it, add a ROA for AS152475.2 of 673
Route object: none79.109.230.0/24Route objects for it name AS137551. Add a route object with origin AS152475 in the RIR database for the space.2 of 673
ROA: origin79.109.231.0/24ROAs covering it name AS137551, not AS152475. If AS152475 should announce it, add a ROA for AS152475.2 of 673
Route object: none79.109.231.0/24Route objects for it name AS137551. Add a route object with origin AS152475 in the RIR database for the space.2 of 673
ROA: maxLength160.30.129.129/32ROA 160.30.129.0/24 AS152475 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 160.30.129.129/32.0 of 673
Route object: none160.30.129.129/32No route object for it. A route object for 160.30.129.0/24 with origin AS152475 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS152475 in the RIR database for the space.0 of 673
ROA: none148.178.127.0/24No ROA covers it. Add a ROA for AS152475, maxLength 24.667 of 673
Route object: RIR148.178.127.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none199.165.238.0/24No ROA covers it. Add a ROA for AS152475, maxLength 24.663 of 673
Route object: RIR199.165.238.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673
Route object: RIR103.152.247.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

38.156.240.0/24RADBNo ROA
103.40.9.0/24APNICValid
103.129.54.0/24APNICValid
103.129.55.0/24APNICValid
113.212.88.0/24APNICValid
2401:bbe0::/32APNICValid
2401:bbe0::/36APNICValid
2401:bbe0:200::/40APNICValid
2407:21c0:9::/48RADBNo 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.