Loopreturns Outage History

17 incidents recorded over the last 365 days, 16 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Loopreturns Incident

Loopreturns incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 4, 2026Delays accessing newly created shipping labelsSince approximately 7:20 AM PST (10:20 AM EST) today, November 4, some Loop merchants may see delays when creating or accessing shipping labels. This is caused by an incident at our shipping provider, EasyPost…1h 48mResolved
Nov 4, 2026UPS OutageWe are experiencing an outage of UPS labels generated through EasyPost5h 26mResolved
Oct 27, 2026Delays syncing returns to BleckmannWe’re seeing elevated errors when sending returns to Bleckmann’s WMS API. Most returns are syncing as normal, but some are not reaching Bleckmann at the moment. The issue is on Bleckmann’s side and we’re monitoring…2h 48mResolved
Oct 19, 2026Degraded Returns PerformanceWe are investigating performance issues in the customer portal and admin. Merchants and Customers may experience degraded performance.20 minResolved
Oct 16, 2026Service Degradation - Label Generation via Bleckmann We've identified a downstream issue with labels being generated / serviced via Bleckmann. We will continue to monitor the downstream degradation for resolution.3h 15mResolved
Oct 15, 2026Possible Rebound Label Provider OutageWe're currently seeing 500 errors from Rebound when attempting to generate labels. We're investigating the root cause of the errors currently30h 40mResolved
Oct 13, 2026Delays generating return shipping labels for Seko carrier returnsWe are investigating an issue affecting return shipping label creation for returns shipped through Seko. Since approximately 10:10 AM CT (15:10 UTC) on October 13, some shoppers have been unable to generate a shipping…1h 19mResolved
Oct 13, 2026Infrastructure Maintenance Window - 2026 Holiday PreparationScheduled Maintenance1h 0mScheduled
Oct 12, 2026Some Shops Being Moved from Active to Passive StatusWe are investigating an issue in-which some shops have been put into a passive versus active status. Preliminary reports indicate this is only impacting around 15 shops, but we are actively confirming this count. More…1h 17mResolved
Oct 5, 2026Customer UX, Admin Portal, and API DisruptionWe're investigating a service disruption across Loop - including shopper user experience, administration portal, and APIs. Updates will be provided within the next 15 minutes.1h 17mResolved
Oct 5, 2026Royal Mail partial disruptionSome shipping providers are experiencing failures related to Royal Mail shipping labels. We are investigating currently and are escalating these issues to the effected providers.52h 21mResolved
Oct 1, 2026Bleckmann Labels DegradedThe Bleckmann Labels API is timing out occasionally, most label requests are successfully being generated and we'll be retrying any failed ones as Bleckmann stabilises.2h 2mResolved
Sep 27, 2026Degraded Returns Performance - Customer and Admin PortalsWe are currently experiencing degraded performance with Customer and Admin Portals and are investigating.1h 15mResolved
Sep 24, 2026USPS Labels failingWe are experiencing service disruption for USPS Label due to api failures. We have alerted Easypost and are monitoring28 minResolved
Sep 20, 2026Label Generation Failures via EasyPost We are investigating an issue in-which one of our third-party label generation providers, EasyPost, is failing to generate shipping labels. Will will report back with updates within 30 minutes or once the issue has…6h 22mResolved
Sep 9, 2026Shopper Portal Network Issue - Impacting Subset of MerchantsA small subset of customers may be experiencing an "Network Error" when attempting to interact with our Shopper Portal. We have identified this issue and are deploying a fix.33 minResolved
Aug 27, 2026Admin login issuesWe've identified an intermittent login issue in our admin and are investigating.2h 8mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Loopreturns incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Loopreturns Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Loopreturns acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Loopreturns outage in this window ran 2d 4h, against a mean recovery of 6h 44m. If you depend on Loopreturns in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.