bgpreport

Network · data from 2026-11-12

AS132541 BETTERWEBCOLTD-AS-AP - Better Web Co., Ltd

Registry name: BETTERWEBCOLTD-AS-AP - Better Web Co., Ltd, TH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS132541, 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.
104.143.217.0/24 Invalid: origin Other origin only 2 0%low visibility 2
104.156.134.0/24 No ROA None 2 0%low visibility 2
104.250.255.0/24 No ROA None 2 0%low visibility 2
216.211.192.0/24 No ROA None 2 0%low visibility 2
216.211.193.0/24 No ROA None 2 0%low visibility 2
66.245.166.0/24 Valid RIR databaseARIN 672 100% 67
94.177.11.0/24 Valid RIR databaseRIPE 672 100% 67
103.99.54.0/24 Valid RIR databaseAPNIC 672 100% 67
165.140.95.0/24 Valid RIR databaseARIN 672 100% 67
201.8.95.0/24 Valid RIR databaseRIPE 672 100% 67
104.164.217.0/24 Valid RIR databaseARIN 670 100% 67
103.115.19.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2
172.120.25.0/24 Valid RIR databaseARIN 2 0%low visibility 2

AS-SET

AS132541 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 12 are in fix.csv.

  • ROA: origin1
  • ROA: none4
  • Route object: none5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin104.143.217.0/24ROAs covering it name AS57043, not AS132541. If AS132541 should announce it, add a ROA for AS132541.2 of 673
Route object: none104.143.217.0/24Route objects for it name AS57043. Add a route object with origin AS132541 in the RIR database for the space.2 of 673
ROA: none104.156.134.0/24No ROA covers it. Add a ROA for AS132541, maxLength 24.2 of 673
Route object: none104.156.134.0/24No route object for it. Add a route object with origin AS132541 in the RIR database for the space.2 of 673
ROA: none104.250.255.0/24No ROA covers it. Add a ROA for AS132541, maxLength 24.2 of 673
Route object: none104.250.255.0/24No route object for it. Add a route object with origin AS132541 in the RIR database for the space.2 of 673
ROA: none216.211.192.0/24No ROA covers it. Add a ROA for AS132541, maxLength 24.2 of 673
Route object: none216.211.192.0/24No route object for it. Add a route object with origin AS132541 in the RIR database for the space.2 of 673
ROA: none216.211.193.0/24No ROA covers it. Add a ROA for AS132541, maxLength 24.2 of 673
Route object: none216.211.193.0/24No route object for it. Add a route object with origin AS132541 in the RIR database for the space.2 of 673

Route objects not announced

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

144.225.241.0/24ARINValid
152.233.111.0/24RIPEInvalid: 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.