Immuta incident
Immuta SaaS Service - Impacting Event Notification
Affected components
Update timeline
- identified Mar 02, 2026, 08:43 PM UTC
We are currently investigating a service disruption affecting the Identification and Classification services within the Immuta SaaS platform. What this means for you: Automatic data detection and column tagging may fail during this period. You may encounter the following error message: “Latest Identification run not successful. Automatic data detection and column tagging did not occur.” Current Status: Our engineering team has identified the root cause and is actively working on a fix to restore full functionality. All other platform services remain operational. We apologize for the interruption. For urgent assistance, please email [email protected] or open a ticket at support.immuta.com.
- identified Mar 02, 2026, 08:51 PM UTC
Our engineering team has identified the root cause and is actively working on a fix to restore full functionality. All other platform services remain operational.
- monitoring Mar 02, 2026, 09:52 PM UTC
A fix have been deployed and we are monitoring the progress. We will work on identifying any jobs that failed and need to be requeued.
- resolved Mar 03, 2026, 03:00 AM UTC
This incident has been resolved.
Looking to track Immuta downtime and outages?
Pingoru polls Immuta's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Immuta reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Immuta alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required