bgpreport

Network · data from 2026-11-12

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

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141883, 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.
148.178.32.0/19 No ROA Other origin only 2 0%low visibility 1
148.178.96.0/24 No ROA None 1 0%low visibility 1

AS-SET

AS141883 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 39 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced35
ChangePrefix or setDetailFull-table peers
ROA: none148.178.32.0/19No ROA covers it. Add a ROA for AS141883, maxLength 19.2 of 673
Route object: none148.178.32.0/19Route objects for it name AS54801, AS139613. Add a route object with origin AS141883 in the RIR database for the space.2 of 673
ROA: none148.178.96.0/24No ROA covers it. Add a ROA for AS141883, maxLength 24.1 of 673
Route object: none148.178.96.0/24No route object for it. Add a route object with origin AS141883 in the RIR database for the space.1 of 673

Route objects not announced

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

45.200.14.0/23AFRINICInvalid: origin
45.200.16.0/23AFRINICInvalid: origin
45.200.18.0/23AFRINICInvalid: origin
45.200.20.0/22AFRINICInvalid: origin
45.200.24.0/21AFRINICInvalid: origin
45.200.32.0/19AFRINICInvalid: origin
45.201.214.0/23AFRINICInvalid: origin
45.201.216.0/21AFRINICInvalid: origin
45.201.224.0/21AFRINICInvalid: origin
45.201.240.0/20AFRINICInvalid: origin
45.204.0.0/24AFRINICInvalid: origin
82.39.172.0/24RADB, RIPEValid
148.178.18.0/24RADBNo ROA
148.178.21.0/24RADBNo ROA
148.178.22.0/24RADBNo ROA
148.178.26.0/23RADBNo ROA
148.178.28.0/23RADBNo ROA
154.86.0.0/24AFRINICInvalid: origin
154.204.0.0/24AFRINICInvalid: origin
154.208.12.0/22AFRINICInvalid: origin
154.208.16.0/20AFRINICInvalid: origin
154.212.128.0/24AFRINICInvalid: origin
154.214.32.0/19RADBNo ROA
154.215.0.0/24AFRINICInvalid: origin
154.218.0.0/24AFRINICInvalid: origin
154.221.0.0/24AFRINICInvalid: origin
156.240.0.0/19AFRINICInvalid: origin
156.240.32.0/20AFRINICInvalid: origin
156.240.48.0/21AFRINICInvalid: origin
156.242.10.0/23AFRINICInvalid: origin
156.242.12.0/22AFRINICInvalid: origin
156.246.0.0/20AFRINICInvalid: origin
156.246.16.0/23AFRINICInvalid: origin
156.249.28.0/22AFRINICInvalid: origin
156.255.0.0/24AFRINICInvalid: origin

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.