Permutive incident
Degraded delivery of segment metadata to streaming Routing BigQuery destinations
Affected components
Update timeline
- monitoring Apr 17, 2026, 01:21 PM UTC
Between 26 March 2026 and 17 April 2026, segment metadata was not being delivered to streaming routing BigQuery destinations. This was identified on 15th April. All other event routing continued to operate normally throughout this period and was unaffected. We have identified the root cause, and a fix has already been rolled out to the affected destinations. A tested backfill solution for segment metadata is available. Please contact [email protected] for more details. We sincerely apologise for the disruption and for the delay in communicating it. As a follow-up, we are investing in improved monitoring so that per-destination write failures are detected proactively in future.
- resolved Apr 20, 2026, 04:34 PM UTC
The fix has been fully rolled out, and segment metadata delivery to streaming Routing BigQuery destinations has been confirmed as restored. All affected destinations are operating normally. A tested backfill solution for segment metadata remains available — please contact [email protected] if you would like us to restore segment metadata for the affected period. Thank you for your patience throughout this incident.
Looking to track Permutive downtime and outages?
Pingoru polls Permutive's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Permutive reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Permutive alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required