bgpreport

Network · data from 2026-11-12

AS210387 GUARDY Guardy Limited

Registry name: GUARDY Guardy Limited, GB · not in PeeringDB

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

Announced routes

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

102.135.86.0/24 No ROA None 1 0%low visibility 1
103.209.78.0/24 No ROA Other origin only 1 0%low visibility 1
104.243.247.0/24 No ROA Other origin only 1 0%low visibility 1
102.135.85.0/24 No ROA None 0 0%low visibility 1
77.90.160.0/24 Valid RIR databaseRIPE 671 100% 66
36.255.96.0/24 Valid RIR databaseAPNIC 670 100% 66
185.169.181.0/24 Valid RIR databaseRIPE 670 100% 67
185.148.241.0/24 Valid RIR databaseRIPE 669 99% 67
192.253.243.0/24 Valid RIR databaseARIN 669 99% 67
206.123.146.0/24 Valid RIR databaseARIN 667 99% 66
185.148.242.0/24 Valid RIR databaseRIPE 664 99% 66

AS-SET

AS210387 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: none4
  • Route object: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none102.135.86.0/24No ROA covers it. Add a ROA for AS210387, maxLength 24.1 of 673
Route object: none102.135.86.0/24No route object for it. Add a route object with origin AS210387 in the RIR database for the space.1 of 673
ROA: none103.209.78.0/24No ROA covers it. Add a ROA for AS210387, maxLength 24.1 of 673
Route object: none103.209.78.0/24Route objects for it name AS9009. Add a route object with origin AS210387 in the RIR database for the space.1 of 673
ROA: none104.243.247.0/24No ROA covers it. Add a ROA for AS210387, maxLength 24.1 of 673
Route object: none104.243.247.0/24Route objects for it name AS132372. Add a route object with origin AS210387 in the RIR database for the space.1 of 673
ROA: none102.135.85.0/24No ROA covers it. Add a ROA for AS210387, maxLength 24.0 of 673
Route object: none102.135.85.0/24No route object for it. Add a route object with origin AS210387 in the RIR database for the space.0 of 673

Route objects not announced

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

45.143.96.0/24RIPEInvalid: origin
2a14:9401:4000::/36RADB, RIPEValid

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.