bgpreport

Network · data from 2026-11-12

AS203866 DC-P2 Versija SIA

Registry name: DC-P2 Versija SIA, LV · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS203866, 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.
213.21.218.201/32 Invalid: maxLength Nonecovered by 213.21.218.0/24 1 0%low visibility 1
213.21.218.202/32 Invalid: maxLength Nonecovered by 213.21.218.0/24 1 0%low visibility 1
213.21.218.203/32 Invalid: maxLength Nonecovered by 213.21.218.0/24 1 0%low visibility 1
213.21.218.204/32 Invalid: maxLength Nonecovered by 213.21.218.0/24 1 0%low visibility 1
213.21.218.205/32 Invalid: maxLength Nonecovered by 213.21.218.0/24 1 0%low visibility 1
176.111.36.0/24 No ROA RIR databaseRIPE 673 100% 67
185.118.76.0/24 Valid RIR databaseRIPE 673 100% 66
193.68.67.0/24 Valid RIR databaseRIPE 673 100% 67
213.21.195.0/24 Valid RIR databaseRIPE 673 100% 66
213.21.218.0/24 Valid RIR databaseRIPE 673 100% 66
45.10.89.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS203866 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: maxLength5
  • ROA: none1
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: maxLength213.21.218.201/32ROA 213.21.218.0/24 AS203866 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 213.21.218.201/32.1 of 673
Route object: none213.21.218.201/32No route object for it. A route object for 213.21.218.0/24 with origin AS203866 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS203866 in the RIR database for the space.1 of 673
ROA: maxLength213.21.218.202/32ROA 213.21.218.0/24 AS203866 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 213.21.218.202/32.1 of 673
Route object: none213.21.218.202/32No route object for it. A route object for 213.21.218.0/24 with origin AS203866 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS203866 in the RIR database for the space.1 of 673
ROA: maxLength213.21.218.203/32ROA 213.21.218.0/24 AS203866 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 213.21.218.203/32.1 of 673
Route object: none213.21.218.203/32No route object for it. A route object for 213.21.218.0/24 with origin AS203866 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS203866 in the RIR database for the space.1 of 673
ROA: maxLength213.21.218.204/32ROA 213.21.218.0/24 AS203866 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 213.21.218.204/32.1 of 673
Route object: none213.21.218.204/32No route object for it. A route object for 213.21.218.0/24 with origin AS203866 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS203866 in the RIR database for the space.1 of 673
ROA: maxLength213.21.218.205/32ROA 213.21.218.0/24 AS203866 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 213.21.218.205/32.1 of 673
Route object: none213.21.218.205/32No route object for it. A route object for 213.21.218.0/24 with origin AS203866 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS203866 in the RIR database for the space.1 of 673
ROA: none176.111.36.0/24No ROA covers it. Add a ROA for AS203866, maxLength 24.673 of 673

Route objects not announced

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