bgpreport

Network · data from 2026-11-12

AS47122 CYBERFIRST-AS CYBERFIRST LLC

Registry name: CYBERFIRST-AS CYBERFIRST LLC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47122, 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.

185.26.213.16/28 No ROA Nonecovered by 185.26.213.0/24 1 0%low visibility 1
185.26.213.32/27 No ROA Nonecovered by 185.26.213.0/24 1 0%low visibility 1
91.214.119.0/24 No ROA RIR databaseRIPE 673 100% 66
185.26.213.0/24 No ROA RIR databaseRIPE 673 100% 66
62.233.46.0/24 Valid RIR databaseRIPE 673 100% 66
193.22.228.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS47122 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 8 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none185.26.213.16/28No ROA covers it. Add a ROA for AS47122, maxLength 28.1 of 673
Route object: none185.26.213.16/28No route object for it. A route object for 185.26.213.0/24 with origin AS47122 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS47122 in the RIR database for the space.1 of 673
ROA: none185.26.213.32/27No ROA covers it. Add a ROA for AS47122, maxLength 27.1 of 673
Route object: none185.26.213.32/27No route object for it. A route object for 185.26.213.0/24 with origin AS47122 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS47122 in the RIR database for the space.1 of 673
ROA: none91.214.119.0/24No ROA covers it. Add a ROA for AS47122, maxLength 24.673 of 673
ROA: none185.26.213.0/24No ROA covers it. Add a ROA for AS47122, maxLength 24.673 of 673

Route objects not announced

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

80.243.78.0/24RIPENo ROA
80.243.79.0/24RIPENo ROA

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.