bgpreport

Network · data from 2026-11-12

AS205373 rightmove Rightmove Group Limited

Registry name: rightmove Rightmove Group Limited, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS205373, 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.220.160.0/24 Valid Other origin onlycovered by 185.220.160.0/22 2 0%low visibility 2
185.220.162.0/24 Valid RIR databaseRIPE 4 1%low visibility 3
185.220.163.0/24 Valid RIR databaseRIPE 4 1%low visibility 3
2a0b:f940::/32 Valid RIR databaseRIPE 3 0%low visibility 3
2a0b:f940:1af2::/48 Valid RIR databaseRIPE 3 0%low visibility 3
2a0b:f940:2af2::/48 Valid RIR databaseRIPE 3 0%low visibility 3
2a0b:f940:4af2::/48 Valid RIR databaseRIPE 3 0%low visibility 3
185.220.160.0/22 Valid RIR databaseRIPE 2 0%low visibility 2
185.220.161.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
2a0b:f940:3af2::/48 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

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

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none185.220.160.0/24Route objects for it name AS19905. A route object for 185.220.160.0/22 with origin AS205373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205373 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS205373 is announced.

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.