bgpreport

Network · data from 2026-11-12

AS206177 sitepark SitePark s.r.o.

Registry name: sitepark SitePark s.r.o., CZ · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS206177, 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.
2a0a:4640:200::/40 No ROA Nonecovered by 2a0a:4640::/29 636 100% 67
2a0a:4640:600::/40 No ROA Nonecovered by 2a0a:4640::/29 636 100% 67
2a0a:4640:1000::/40 No ROA Nonecovered by 2a0a:4640::/29 636 100% 67
2a0a:4640:1200::/40 No ROA Nonecovered by 2a0a:4640::/29 636 100% 67
2a0a:4640:2000::/40 No ROA Nonecovered by 2a0a:4640::/29 636 100% 67
2a0a:4640:900::/40 No ROA Nonecovered by 2a0a:4640::/29 635 100% 67
185.194.68.0/22 No ROA RIR databaseRIPE 671 100% 66
2a0a:4640::/29 No ROA RIR databaseRIPE 634 100% 67

AS-SET

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

  • ROA: none8
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: none2a0a:4640:200::/40No ROA covers it. Add a ROA for AS206177, maxLength 40.636 of 636
Route object: none2a0a:4640:200::/40No route object for it. A route object for 2a0a:4640::/29 with origin AS206177 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206177 in the RIR database for the space.636 of 636
ROA: none2a0a:4640:600::/40No ROA covers it. Add a ROA for AS206177, maxLength 40.636 of 636
Route object: none2a0a:4640:600::/40No route object for it. A route object for 2a0a:4640::/29 with origin AS206177 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206177 in the RIR database for the space.636 of 636
ROA: none2a0a:4640:1000::/40No ROA covers it. Add a ROA for AS206177, maxLength 40.636 of 636
Route object: none2a0a:4640:1000::/40No route object for it. A route object for 2a0a:4640::/29 with origin AS206177 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206177 in the RIR database for the space.636 of 636
ROA: none2a0a:4640:1200::/40No ROA covers it. Add a ROA for AS206177, maxLength 40.636 of 636
Route object: none2a0a:4640:1200::/40No route object for it. A route object for 2a0a:4640::/29 with origin AS206177 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206177 in the RIR database for the space.636 of 636
ROA: none2a0a:4640:2000::/40No ROA covers it. Add a ROA for AS206177, maxLength 40.636 of 636
Route object: none2a0a:4640:2000::/40No route object for it. A route object for 2a0a:4640::/29 with origin AS206177 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206177 in the RIR database for the space.636 of 636
ROA: none2a0a:4640:900::/40No ROA covers it. Add a ROA for AS206177, maxLength 40.635 of 636
Route object: none2a0a:4640:900::/40No route object for it. A route object for 2a0a:4640::/29 with origin AS206177 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206177 in the RIR database for the space.635 of 636
ROA: none185.194.68.0/22No ROA covers it. Add a ROA for AS206177, maxLength 22.671 of 673
ROA: none2a0a:4640::/29No ROA covers it. Add a ROA for AS206177, maxLength 29.634 of 636

Route objects not announced

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