Loop Returns incident

Split-fulfillment returns with package-protection-like products, such as Protect+ unable to be submitted

Minor Resolved View vendor source →
Started
Apr 29, 2026, 06:37 PM UTC
Resolved
Apr 29, 2026, 08:52 PM UTC
Duration
2h 15m
Detected by Pingoru
Apr 29, 2026, 06:37 PM UTC

Affected components

Returns Portal3rd Party Integrations (Loop)

Update timeline

  1. investigating Apr 29, 2026, 06:37 PM UTC

    We have identified an edge case where split-fulfillment returns with package-protection-like products, such as Protect+ are unable to be submitted in the returns portal. We are currently investigating to determine impact and root cause.

  2. investigating Apr 29, 2026, 06:54 PM UTC

    We are still investigating.

  3. investigating Apr 29, 2026, 07:11 PM UTC

    We are still investigating - we have identified a potential root cause and are validating this.

  4. investigating Apr 29, 2026, 07:29 PM UTC

    Still investigating .

  5. investigating Apr 29, 2026, 07:58 PM UTC

    We determined our initial potential root cause was not the correct one. We are confirming a different potential root cause by rolling back a recent code change.

  6. investigating Apr 29, 2026, 08:18 PM UTC

    The code revert is being deployed.

Looking to track Loop Returns downtime and outages?

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

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

5 free monitors · No credit card required