bgpreport

Network · data from 2026-11-12

AS8207 AS8207 PRIVATE JOINT STOCK COMPANY "DATAGROUP"

Registry name: AS8207 PRIVATE JOINT STOCK COMPANY "DATAGROUP", UA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8207, 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.
195.114.128.216/32 Invalid: maxLength Nonecovered by 195.114.128.0/24 3 0%low visibility 6
195.114.128.0/24 Valid RIR databaseRIPE 673 100% 66
195.114.129.0/24 Valid RIR databaseRIPE 673 100% 66
195.114.135.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS8207 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 5 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength195.114.128.216/32ROA 195.114.128.0/24 AS8207 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 195.114.128.216/32.3 of 673
Route object: none195.114.128.216/32No route object for it. A route object for 195.114.128.0/24 with origin AS8207 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS8207 in the RIR database for the space.3 of 673

Route objects not announced

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

195.114.128.0/20RIPEInvalid: origin
195.114.133.0/24RIPEInvalid: origin
195.114.144.0/24RIPEInvalid: origin

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.