Blueshift incident

Observing backlogs in segmentation data

Resolved after 3 hours 16 minutes, affecting Segments, on April 3, 2025.

monitoring Apr 03, 2025, 02:00 PM UTC

The system is stable now but the backlogs will take some time to get processed. Keeping this incident open until backlogs are done.

Started
Apr 03, 2025, 01:15 PM UTC
Resolved
Apr 03, 2025, 04:32 PM UTC
Duration
3h 16m
Detected by Pingoru
Apr 03, 2025, 01:15 PM UTC

Affected components

Segments

Update timeline

  1. investigating Apr 03, 2025, 01:15 PM UTC

    Observing backlogs in segmentation data processing. This will manifest as delayed data visibility during segmentation.

  2. identified Apr 03, 2025, 01:19 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 03, 2025, 02:00 PM UTC

    The system is stable now but the backlogs will take some time to get processed. Keeping this incident open until backlogs are done.

  4. resolved Apr 03, 2025, 04:32 PM UTC

    This incident has been resolved.

Your product runs on more than Blueshift

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →