bgpreport

Network · data from 2026-11-12

AS214927 PSB-AS PSB HOSTING LTD

Registry name: PSB-AS PSB HOSTING LTD, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS214927, 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.
185.122.171.0/24 Invalid: origin Other origin only 19 3%low visibility 19
45.129.125.0/24 Invalid: origin None 15 2%low visibility 16
85.209.128.0/24 No ROA None 2 0%low visibility 2
82.115.223.0/24 Valid RIR databaseRIPE 671 100% 67
94.232.249.0/24 Valid RIR databaseRIPE 671 100% 67
185.242.245.0/24 Valid RIR databaseRIPE 671 100% 67
45.155.69.0/24 Valid RIR databaseRIPE 670 100% 67
2a0c:7886:105::/48 Valid RIR databaseRIPE 634 100% 68
2a0f:e7c6:1000::/48 Valid RIR databaseRIPE 634 100% 68
193.124.185.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

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

  • ROA: origin2
  • ROA: none1
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin185.122.171.0/24ROAs covering it name AS60781, not AS214927. If AS214927 should announce it, add a ROA for AS214927.19 of 673
Route object: none185.122.171.0/24Route objects for it name AS60781. Add a route object with origin AS214927 in the RIR database for the space.19 of 673
ROA: origin45.129.125.0/24ROAs covering it name AS213334, not AS214927. If AS214927 should announce it, add a ROA for AS214927.15 of 673
Route object: none45.129.125.0/24No route object for it. Add a route object with origin AS214927 in the RIR database for the space.15 of 673
ROA: none85.209.128.0/24No ROA covers it. Add a ROA for AS214927, maxLength 24.2 of 673
Route object: none85.209.128.0/24No route object for it. Add a route object with origin AS214927 in the RIR database for the space.2 of 673

Route objects not announced

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

185.106.92.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.