bgpreport

Network · data from 2026-11-12

AS199458 rusbuilding LLC Rusbuilding

Registry name: rusbuilding LLC Rusbuilding, RU · not in PeeringDB

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

Announced routes

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

45.137.63.0/24 Invalid: origin Other origin only 33 5%low visibility 22
45.142.31.0/24 Invalid: origin Other origin only 3 0%low visibility 3
149.18.66.0/24 Valid Nonecovered by 149.18.66.0/23 673 100% 66
149.18.67.0/24 Valid Nonecovered by 149.18.66.0/23 673 100% 66
149.57.53.0/24 Valid RIR databaseARIN, RADB 673 100% 66
45.8.179.0/24 Valid RIR databaseRIPE 672 100% 66
45.92.171.0/24 Valid RIR databaseRIPE 672 100% 67
206.123.140.0/24 Valid RIR databaseARIN 671 100% 67

AS-SET

AS199458 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: origin2
  • Route object: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin45.137.63.0/24ROAs covering it name AS60781, not AS199458. If AS199458 should announce it, add a ROA for AS199458.33 of 673
Route object: none45.137.63.0/24Route objects for it name AS60781. Add a route object with origin AS199458 in the RIR database for the space.33 of 673
ROA: origin45.142.31.0/24ROAs covering it name AS215540, not AS199458. If AS199458 should announce it, add a ROA for AS199458.3 of 673
Route object: none45.142.31.0/24Route objects for it name AS215540. Add a route object with origin AS199458 in the RIR database for the space.3 of 673
Route object: none149.18.66.0/24No route object for it. A route object for 149.18.66.0/23 with origin AS199458 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199458 in the RIR database for the space.673 of 673
Route object: none149.18.67.0/24No route object for it. A route object for 149.18.66.0/23 with origin AS199458 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199458 in the RIR database for the space.673 of 673

Route objects not announced

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

45.159.92.0/22RIPEValid
149.18.66.0/23ARIN, RADBValid

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.