Batch incident

Processing Delays for Mobile Profile Updates

Minor Resolved View vendor source →
Started
Feb 21, 2026, 07:43 PM UTC
Resolved
Feb 21, 2026, 11:17 PM UTC
Duration
3h 34m
Detected by Pingoru
Feb 21, 2026, 07:43 PM UTC

Update timeline

  1. resolved Feb 21, 2026, 11:17 PM UTC

    Feb 21, 23:17 UTC Resolved - This incident has been resolved. Feb 21, 21:19 UTC Monitoring - The processing backlog has been steadily decreasing over the last hour. We continue to monitor the situation closely until all updates are processed and real-time performance is restored. Feb 21, 20:16 UTC Identified - We have identified the issue and deployed a fix. The processing backlog is now beginning to clear, and delivery delays are steadily decreasing. We are monitoring the pipeline closely to ensure performance returns to nominal levels. Feb 21, 19:43 UTC Investigating - We are investigating a performance degradation within our profile processing pipeline. This issue specifically affects updates sent via our mobile SDKs. As of 21/02/2026 at 17:00 CET, processing times have increased, with current delays of up to 3 hours. This latency may result in delayed execution for triggered automations.

Looking to track Batch downtime and outages?

Pingoru polls Batch's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Batch reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Batch alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Batch for free

5 free monitors · No credit card required