bgpreport

Network · data from 2026-11-12

AS206680 Consumer Internet Cooperative PG-19 - AS206680

Registry name: PG19-Rovenki Consumer Internet Cooperative PG-19, RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS206680, 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.
80.72.22.0/24 Valid Nonecovered by 80.72.22.0/23 2 0%low visibility 2
2a00:8740:700::/40 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS206680's PeeringDB record names no 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 2 are in fix.csv.

  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none80.72.22.0/24No route object for it. A route object for 80.72.22.0/23 with origin AS206680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206680 in the RIR database for the space.2 of 673

Route objects not announced

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

80.72.22.0/23RIPEValid

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.