bgpreport

Network · data from 2026-11-12

AS201002 PebbleHost-Customers PebbleHost Ltd

Registry name: PebbleHost-Customers PebbleHost Ltd, GB · not in PeeringDB

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

Announced routes

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

167.148.126.0/24 Invalid: origin Other origin only 1 0%low visibility 1
62.171.251.0/24 No ROA Other origin only 2 0%low visibility 2
94.103.189.0/24 No ROA None 2 0%low visibility 2
82.152.184.0/24 Valid Other IRR onlyRADB 673 100% 67
41.216.187.0/24 Valid RIR databaseAFRINIC 673 100% 67
63.142.247.0/24 Valid RIR databaseARIN 673 100% 67
82.38.128.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
82.139.192.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
94.103.191.0/24 Valid RIR databaseRIPE 673 100% 67
138.249.24.0/24 Valid RIR databaseRIPE 673 100% 67
138.249.25.0/24 Valid RIR databaseRIPE 673 100% 67
138.249.26.0/24 Valid RIR databaseRIPE 673 100% 67
138.249.32.0/24 Valid RIR databaseRIPE 673 100% 67
138.249.33.0/24 Valid RIR databaseRIPE 673 100% 67
138.249.34.0/24 Valid RIR databaseRIPE 673 100% 67
138.249.35.0/24 Valid RIR databaseRIPE 673 100% 67
138.249.40.0/24 Valid RIR databaseRIPE 673 100% 67
138.249.41.0/24 Valid RIR databaseRIPE 673 100% 67
138.249.42.0/24 Valid RIR databaseRIPE 673 100% 67
138.249.43.0/24 Valid RIR databaseRIPE 673 100% 67
138.249.135.0/24 Valid RIR databaseRIPE 673 100% 67
141.133.140.0/24 Valid RIR databaseRIPE 673 100% 67
141.133.141.0/24 Valid RIR databaseRIPE 673 100% 67
185.83.203.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
193.8.186.0/24 Valid RIR databaseRIPE 673 100% 67
198.244.13.0/24 Valid RIR databaseARIN 673 100% 67
198.244.14.0/24 Valid RIR databaseARIN 673 100% 67
198.244.15.0/24 Valid RIR databaseARIN 673 100% 67
212.80.6.0/24 Valid RIR databaseRIPE 673 100% 67
212.189.96.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
212.192.213.0/24 Valid RIR databaseRIPE 673 100% 67
217.60.108.0/24 Valid RIR databaseRIPE 673 100% 67
217.60.109.0/24 Valid RIR databaseRIPE 673 100% 67
217.60.110.0/24 Valid RIR databaseRIPE 673 100% 67
217.60.111.0/24 Valid RIR databaseRIPE 673 100% 67
217.60.112.0/24 Valid RIR databaseRIPE 673 100% 67
217.60.113.0/24 Valid RIR databaseRIPE 673 100% 67
217.60.114.0/24 Valid RIR databaseRIPE 673 100% 67
217.60.115.0/24 Valid RIR databaseRIPE 673 100% 67
217.60.116.0/24 Valid RIR databaseRIPE 673 100% 67
217.60.117.0/24 Valid RIR databaseRIPE 673 100% 67
217.60.118.0/24 Valid RIR databaseRIPE 673 100% 67
217.60.119.0/24 Valid RIR databaseRIPE 673 100% 67
45.85.61.0/24 Valid RIR databaseRIPE 672 100% 67
64.49.11.0/24 Valid RIR databaseARIN 672 100% 67
38.252.207.0/24 Valid RIR databaseARIN 671 100% 67
82.39.133.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
2a06:9801:250::/44 Valid RIR databaseRIPE 635 100% 69
2a10:e781::/40 Valid RIR databaseRIPE 635 100% 69
2a0e:15c4::/32 Valid RIR databaseRIPE 634 100% 69
2a13:9500:10e::/48 Valid RIR databaseRIPE 634 100% 69

AS-SET

AS201002 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 10 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin167.148.126.0/24ROAs covering it name AS834, not AS201002. If AS201002 should announce it, add a ROA for AS201002.1 of 673
Route object: none167.148.126.0/24Route objects for it name AS834. Add a route object with origin AS201002 in the RIR database for the space.1 of 673
ROA: none62.171.251.0/24No ROA covers it. Add a ROA for AS201002, maxLength 24.2 of 673
Route object: none62.171.251.0/24Route objects for it name AS834. Add a route object with origin AS201002 in the RIR database for the space.2 of 673
ROA: none94.103.189.0/24No ROA covers it. Add a ROA for AS201002, maxLength 24.2 of 673
Route object: none94.103.189.0/24No route object for it. Add a route object with origin AS201002 in the RIR database for the space.2 of 673
Route object: RIR82.152.184.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

185.183.182.0/24RIPEValid
185.185.126.0/24RIPEValid
185.189.27.0/24RIPEValid

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.