Zipline Outage History

Zipline is up right now

Zipline had 9 outages in the last 2 years totaling 77h 15m of downtime — averaging 0.4 incidents per month.

There were 9 Zipline outages since June 6, 2024 totaling 77h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.retailzipline.com

Minor April 3, 2026

Intermittent Performance Degradation — Zipline Application

Detected by Pingoru
Apr 03, 2026, 10:15 PM UTC
Resolved
Apr 03, 2026, 11:09 PM UTC
Duration
53m
Affected: Core Platform
Timeline · 3 updates
  1. identified Apr 03, 2026, 10:15 PM UTC

    We are currently investigating intermittent slowness and elevated response times affecting the Zipline application. Some users may experience delays when loading pages or an error screen. Our team has identified the issue and is actively deploying a fix. We will provide an update as soon as possible. We apologize for the disruption and appreciate your patience.

  2. monitoring Apr 03, 2026, 10:40 PM UTC

    A fix has been deployed to address the performance issue affecting the Zipline application. The platform is currently stable and we are monitoring closely to confirm full resolution. We will update this page once we are confident the issue has been fully resolved. We apologize for the disruption today and appreciate your patience.

  3. resolved Apr 03, 2026, 11:09 PM UTC

    This incident has been fully resolved. The Zipline application is operating normally and all systems are performing as expected. We apologize for the disruption experienced today and will be conducting a thorough review to prevent recurrence. Thank you for your patience.

Read the full incident report →

Major October 20, 2025

Widespread AWS Outage Impacting Access to Zipline

Detected by Pingoru
Oct 20, 2025, 02:53 PM UTC
Resolved
Oct 20, 2025, 11:02 PM UTC
Duration
8h 8m
Affected: Core PlatformLogin/SSOGraphQL APISearchEmail Handling3rd Party ApplicationsPublishingZippyNotificationsFilesInsightsResource LibraryMobile App - AndroidMobile App - iOS
Timeline · 6 updates
  1. investigating Oct 20, 2025, 02:53 PM UTC

    As a result of the current ongoing widespread outage with Amazon Web Services (AWS) access to Zipline may be impacted along with certain functionality within the application. We are currently assessing all the areas of impact and working to mitigate and or resolve.

  2. identified Oct 20, 2025, 02:57 PM UTC

    AWS US-East-1 is experiencing a major outage impacting a portion of Zipline services and large parts of the Internet. We’re actively monitoring their status updates and will share new information as soon as it becomes available

  3. identified Oct 20, 2025, 04:05 PM UTC

    Our teams are closely monitoring our service providers updates (AWS). AWS is indicating that they've identified the connectivity issue on their end and implementing mitigation and remediation steps. A link to AWS health status can be found here: https://health.aws.amazon.com/health/status

  4. identified Oct 20, 2025, 06:29 PM UTC

    Our teams continue to closely monitor updates from our service provider (AWS). They have indicated that they are in the midst of a full recovery. At this time, our internal monitoring confirms site-wide stability across all Zipline services. We will continue to observe system performance closely to ensure sustained reliability and will provide additional updates upon full resolution.

  5. monitoring Oct 20, 2025, 09:27 PM UTC

    We are confident in the latest updates from Amazon Web Services (AWS), they are close to a full resolution. Our team has been able to confirm that for the last hour and a half we are seeing full site wide stability. We will continue to monitor until we recieve a full resolution from AWS status page.

  6. resolved Oct 20, 2025, 11:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 28, 2025

DO NOT INSTALL Zipline for iOS, Build 4.1.4 (Please!)

Detected by Pingoru
Aug 28, 2025, 01:04 AM UTC
Resolved
Aug 28, 2025, 02:22 PM UTC
Duration
13h 18m
Affected: Mobile App - iOS
Timeline · 2 updates
  1. identified Aug 28, 2025, 01:04 AM UTC

    The most recent build of our iOS app, build 4.1.4, was corrupted during the build and deploy process, and will not function properly if installed on devices. Unfortunately, we cannot roll back the version in the Apple store. We are already working on deploying a fix in version 4.1.5. We anticipate that the fix will be deployed tomorrow. In the meantime, please avoid deploying 4.1.4 to devices if at all possible, as it will render Zipline non-operational on those devices. Thank you for your patience and understanding as we work to resolve this issue.

  2. resolved Aug 28, 2025, 02:22 PM UTC

    Resolved: We were able to expedite the release of a new version of the iOS app, 4.1.5 and it is working as expected. If you made the upgrade to 4.1.4 please update the app to bump your version to a non-corrupt version of the Zipline iOS app in the App Store. If you hadn't installed the latest version from us that was released on August 27th you will not be and haven't been affected.

Read the full incident report →

Notice April 24, 2025

Incorrect Zipline Module Availability

Detected by Pingoru
Apr 24, 2025, 08:23 PM UTC
Resolved
Apr 24, 2025, 11:36 PM UTC
Duration
3h 13m
Affected: Core PlatformLogin/SSOGraphQL APISearch3rd Party ApplicationsPublishingZippyNotificationsFilesInsightsResource Library
Timeline · 3 updates
  1. identified Apr 24, 2025, 08:23 PM UTC

    We have identified an issue in the Zipline app where customers will see modules that they have not previously had access to. We have identified the root cause and are working towards a resolution. While this is ongoing there might be unintended interactions with the app.

  2. monitoring Apr 24, 2025, 10:42 PM UTC

    A fix has been implemented by our engineering team. Most customers should notice that the correct Zipline modules are now appearing once again. We will continue to monitor the situation closely and provide the next update upon full resolution.

  3. resolved Apr 24, 2025, 11:36 PM UTC

    This incident has now been fully resolved and all Zipline modules are displaying correctly.

Read the full incident report →

Major December 12, 2024

Upstream incident affecting Zippy Availability

Detected by Pingoru
Dec 12, 2024, 03:08 AM UTC
Resolved
Dec 12, 2024, 08:38 AM UTC
Duration
5h 29m
Affected: Zippy
Timeline · 3 updates
  1. identified Dec 12, 2024, 03:08 AM UTC

    Our upstream provider is currently experiencing downtime, which is affecting Zippy Availability. The incident is posted here: https://status.openai.com/incidents/ctrsv3lwd797

  2. monitoring Dec 12, 2024, 04:00 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Dec 12, 2024, 08:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 25, 2024

Intermittent Connection Errors in the European Environment

Detected by Pingoru
Jul 25, 2024, 07:47 AM UTC
Resolved
Jul 25, 2024, 08:27 AM UTC
Duration
39m
Affected: Core Platform
Timeline · 3 updates
  1. identified Jul 25, 2024, 06:54 AM UTC

    Impact: Intermittent connection errors affecting approximately 20% of requests Details: We are currently experiencing intermittent connection errors in our European environment. Approximately 20% of requests are returning error pages. Refreshing the page solves the issue. Our investigation indicates that the issue is related to an upstream provider. Actions Taken: - Our team is working with our upstream provider to identify and resolve the issue. - We are monitoring the situation closely and will provide updates once we have more information. We apologize for any inconvenience this may cause and appreciate your patience as we work to restore normal service. Next Update: We will provide the next update when progress is made.

  2. monitoring Jul 25, 2024, 07:47 AM UTC

    All requests have succeeded since 00:12 PDT / 9:12am UTC. We are waiting for a confirmation from our upstream provider that the issue is fully resolved on their end.

  3. resolved Jul 25, 2024, 08:27 AM UTC

    This incident has been resolved. All requests have succeeded since 00:12 PDT / 9:12 am UTC. Our upstream provider has confirmed that the issue is resolved on their end.

Read the full incident report →

Major June 6, 2024

Partial outage: clock punches

Detected by Pingoru
Jun 06, 2024, 04:23 PM UTC
Resolved
Jun 06, 2024, 04:34 PM UTC
Duration
11m
Affected: 3rd Party Applications
Timeline · 2 updates
  1. investigating Jun 06, 2024, 04:23 PM UTC

    We are currently investigating an issue with a downstream provider, where clock punches do not seem to be accessible to our API

  2. resolved Jun 06, 2024, 04:34 PM UTC

    This incident has been resolved.

Read the full incident report →