CapaSystems CapaOne incident
CapaOne Agent 132 is not signed correctly
Affected components
CapaOne Privileges
Update timeline
- identified Feb 19, 2026, 08:58 AM UTC
We have identified that Agent 132 is not signed correctly. Because of this, the agent may be flagged as a potential virus by antivirus or security software. The issue is related to the code-signing of the agent and is currently being investigated. An updated, correctly signed version will be provided.
- monitoring Feb 19, 2026, 11:06 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 20, 2026, 12:41 PM UTC
This issue is resolved in Agent 139, which is correctly signed and should no longer trigger false-positive detections.
Looking to track CapaSystems CapaOne downtime and outages?
Pingoru polls CapaSystems CapaOne's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when CapaSystems CapaOne reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track CapaSystems CapaOne alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
Start monitoring CapaSystems CapaOne for free
5 free monitors · No credit card required