bgpreport

Network · data from 2026-11-12

AS207133 RUCOMTECH

Registry name: RUCOMTECH-AS RUCOMTECH LLC, RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207133, 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.160.216.0/22 No ROA RIR databaseRIPE 673 100% 66
185.250.48.0/22 No ROA RIR databaseRIPE 673 100% 66
2a04:2bc0::/32 No ROA RIR databaseRIPE 636 100% 68
2a0c:78c0::/29 No ROA RIR databaseRIPE 635 100% 68

AS-SET

AS207133'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 4 are in fix.csv.

  • ROA: none4
ChangePrefix or setDetailFull-table peers
ROA: none185.160.216.0/22No ROA covers it. Add a ROA for AS207133, maxLength 22.673 of 673
ROA: none185.250.48.0/22No ROA covers it. Add a ROA for AS207133, maxLength 22.673 of 673
ROA: none2a04:2bc0::/32No ROA covers it. Add a ROA for AS207133, maxLength 32.636 of 636
ROA: none2a0c:78c0::/29No ROA covers it. Add a ROA for AS207133, maxLength 29.635 of 636

Route objects not announced

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