bgpreport

Network · data from 2026-11-12

AS201650 webguru Webguru VOF

Registry name: webguru Webguru VOF, NL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS201650, 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.
2a03:28a0:4::/48 No ROA Nonecovered by 2a03:28a0::/32 635 100% 67
185.68.96.0/22 No ROA RIR databaseRIPE 673 100% 66
185.68.97.0/24 No ROA RIR databaseRIPE 673 100% 66
185.68.98.0/24 No ROA RIR databaseRIPE 673 100% 66
185.68.99.0/24 No ROA RIR databaseRIPE 673 100% 66
2a03:28a0:3::/48 No ROA RIR databaseRIPE 635 100% 67
2a03:28a0::/32 No ROA RIR databaseRIPE 633 100% 67
2a03:28a0:2::/48 No ROA RIR databaseRIPE 633 100% 67
2a03:28a0:1::/48 No ROA RIR databaseRIPE 390 61% 64
185.68.96.0/24 No ROA RIR databaseRIPE 271 40% 57

AS-SET

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

  • ROA: none10
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none2a03:28a0:4::/48No ROA covers it. Add a ROA for AS201650, maxLength 48.635 of 636
Route object: none2a03:28a0:4::/48No route object for it. A route object for 2a03:28a0::/32 with origin AS201650 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201650 in the RIR database for the space.635 of 636
ROA: none185.68.96.0/22No ROA covers it. Add a ROA for AS201650, maxLength 22.673 of 673
ROA: none185.68.97.0/24No ROA covers it. Add a ROA for AS201650, maxLength 24.673 of 673
ROA: none185.68.98.0/24No ROA covers it. Add a ROA for AS201650, maxLength 24.673 of 673
ROA: none185.68.99.0/24No ROA covers it. Add a ROA for AS201650, maxLength 24.673 of 673
ROA: none2a03:28a0:3::/48No ROA covers it. Add a ROA for AS201650, maxLength 48.635 of 636
ROA: none2a03:28a0::/32No ROA covers it. Add a ROA for AS201650, maxLength 32.633 of 636
ROA: none2a03:28a0:2::/48No ROA covers it. Add a ROA for AS201650, maxLength 48.633 of 636
ROA: none2a03:28a0:1::/48No ROA covers it. Add a ROA for AS201650, maxLength 48.390 of 636
ROA: none185.68.96.0/24No ROA covers it. Add a ROA for AS201650, maxLength 24.271 of 673

Route objects not announced

Every route object with origin AS201650 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.