Zipline Outage History

Started Apr 09, 2026, 08:58 PM UTC· resolved Apr 10, 2026, 09:06 PM UTC

1. investigating Apr 09, 2026, 08:58 PM UTC

   We are aware of an issue affecting search indexing performance. Some customers may experience the following: • Delays in newly published communications appearing in bundles or published tabs • Search results that are temporarily out of date (e.g., archived content still appearing, or recently updated titles not yet reflected) Important: Publishing, document creation, and all core platform functionality remain fully operational. This issue is limited to the speed at which search indexes reflect recent changes and the majority of users won't be impacted. Our engineering team has identified the underlying cause and is actively deploying a short term fix to restore normal indexing performance and prioritizing and working towards a longer term fix. There will be no data loss. We will post another update within 60 minutes or sooner as the situation progresses.

2. investigating Apr 09, 2026, 09:09 PM UTC

   We are continuing to investigate this issue.

3. identified Apr 09, 2026, 09:11 PM UTC

   We are aware of an issue affecting search indexing performance. Some customers may experience the following: • Delays in newly published communications appearing in bundles or published tabs • Search results that are temporarily out of date (e.g., archived content still appearing, or recently updated titles not yet reflected) Important: Publishing, document creation, and all core platform functionality remain fully operational. This issue is limited to the speed at which search indexes reflect recent changes and the majority of users won't be impacted. Our engineering team has identified the underlying cause and is actively deploying a short term fix to restore normal indexing performance and prioritizing and working towards a longer term fix. There will be no data loss. We will post another update within 60 minutes or sooner as the situation progresses.

4. identified Apr 09, 2026, 10:20 PM UTC

   Update: We are actively deploying a fix that will resolve the publisher bundle and published tab visibility issues and improve search indexing performance. Publishing, document creation, and all core platform functionality remain fully operational. There will be no data loss. We will post another update once the fix is confirmed in production.

5. identified Apr 10, 2026, 12:19 AM UTC

   Update: We have identified the root cause of this issue and have a plan in place. Publisher bundles, published tabs, and communications are no longer impacted, we have deployed a change that restores normal behavior for publishers. Resource Library document search remains operational. However, as part of our stabilization work, indexing of new Resource Library Documents has been temporarily paused to preserve overall platform search stability. Existing documents remain searchable. Updates to document metadata may not immediately be reflected in search results but the documents are still searchable. Our engineering team is dedicated to a targeting a fix for tomorrow that we believe will fully resolve the underlying issue and allow us to resume normal attachment indexing with no backfilling required. Again there is no data loss. We will post an update tomorrow as that work progresses.

6. identified Apr 10, 2026, 05:02 PM UTC

   Update: Our engineering team has identified a resolution and is in the process of validating and deploying it. The fix targets the root cause of the attachment indexing degradation and will allow us to safely resume document indexing for Resource Library search. Since yesterday evening platform performance is healthy. Once validated, we will re-enable indexing and work through the accumulated backlog. Customers should expect Resource Library search to gradually reflect recent changes over the following hours as the queue drains. All other functionality: publishing, communications, bundles, published tabs, and document creation remains fully operational. There will be no data loss. We will post a final update once indexing has been fully restored.

7. monitoring Apr 10, 2026, 07:59 PM UTC

   Update: The fix has been deployed and Resource Library document indexing has been re-enabled. The indexing backlog is processing and search results will continue to reflect recent changes over the next few hours as the queue works through accumulated jobs. We are actively monitoring ElasticSearch performance to confirm full stability. All platform functionality: publishing, communications, bundles, published tabs, and document creation remains fully operational. There has been no data loss. We will post a final update once we have confirmed the incident is fully resolved.

8. resolved Apr 10, 2026, 09:06 PM UTC

   Resolved: This incident has been resolved. The fix has been deployed and the indexing backlog has been processed. Publisher bundles, published tabs, communications, and Resource Library search are all operating normally. ElasticSearch performance has returned to a healthy state and there has been no data loss. We appreciate your patience while our team worked through this. We will be conducting a full post-incident review and implementing longer-term improvements to prevent a recurrence.

Read the full incident report →

Started Apr 03, 2026, 10:15 PM UTC· resolved Apr 03, 2026, 11:09 PM UTC

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 →

Started Oct 20, 2025, 02:53 PM UTC· resolved Oct 20, 2025, 11:02 PM UTC

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 →

Started Aug 28, 2025, 01:04 AM UTC· resolved Aug 28, 2025, 02:22 PM UTC

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 →

Started Jun 10, 2025, 12:51 PM UTC· resolved Jun 11, 2025, 10:03 AM UTC

1. monitoring Jun 10, 2025, 12:51 PM UTC

   Our hosting provider, Heroku, is currently investigating an issue in their platform, which hosts the Zipline app: https://status.salesforce.com/generalmessages/10001540 https://status.heroku.com/incidents/2822 As a result of this upstream issue, our engineers currently do not have access to many of the tools that allow us to manage system load, and we understand that the systems which "autoscale" new resources to handle busy peaks may also be offline. While this issue is ongoing, it's possible that our service will be degraded as it becomes busier over the course of the day. We will continue to directly monitor Heroku's (so far scant) information regarding the causes and likely resolution time for this incident.

2. monitoring Jun 10, 2025, 02:14 PM UTC

   We are continuing to monitor the situation closely with the utmost urgency as our top priority at this time. To recap, Zipline is currently impacted by a major upstream outage being experienced by our hosting provider Heroku (A Salesforce Company). More details on that can be found here: https://status.salesforce.com/generalmessages/10001540 Depending on the Zipline cluster where your organization is being hosted (i.e. NA, EU, etc.) you may be having a different experience simply based on the differences in overall traffic/volume/load. Generally speaking though, attempts to reload, refresh or log out and back in to the application will not serve useful. Our teams will continue to remain close to this issue and provide updates via this channel as soon as they are available. We apologize for any inconveniences or disruptions this may be causing to your day to day operations.

3. monitoring Jun 10, 2025, 02:32 PM UTC

   We are continuing to monitor for any further issues.

4. monitoring Jun 10, 2025, 02:33 PM UTC

   We are continuing to monitor the situation closely with the utmost urgency as our top priority at this time. To recap, Zipline is currently impacted by a major upstream outage being experienced by our hosting provider Heroku (A Salesforce Company). More details on that can be found here: https://status.salesforce.com/generalmessages/10001540 Depending on the Zipline cluster where your organization is being hosted (i.e. NA, EU, etc.) you may be having a different experience simply based on the differences in overall traffic/volume/load. Generally speaking though, attempts to reload, refresh or log out and back in to the application will not serve useful. Our teams will continue to remain close to this issue and provide updates via this channel as soon as they are available. We apologize for any inconveniences or disruptions this may be causing to your day to day operations.

5. monitoring Jun 10, 2025, 03:09 PM UTC

   Within the last 20 minutes, Salesforce has began rebooting affected Heroku instances and claim that this should restore service. We are seeing error rates drop across our hosting infrastructure, and will continue monitoring closely until we are confident that service is fully normalized.

6. monitoring Jun 10, 2025, 03:19 PM UTC

   It appears that Salesforce have identified the root cause of the issue, but have yet to fully resolve it. From their status updates (https://status.salesforce.com/generalmessages/10001540): "Some customers are seeing improvements while accessing their services; however, the current impact still remains. Further investigations highlighted that an automated change on the Heroku environment was the potential trigger of this issue."

7. monitoring Jun 10, 2025, 03:45 PM UTC

   We are currently seeing a significant improvement in the responsiveness of our underlying Heroku services, and the stability of our applications as a result. Our team now also has at least partial access to the tools we need to manage our system resources effectively. We will continue to monitor this as an active incident until Salesforce/Heroku give a definitive "all clear" on their systems.

8. monitoring Jun 10, 2025, 04:48 PM UTC

   We are confident that we're now able to absorb the worst of the impacts from Heroku's ongoing instability, but cannot guarantee uninterrupted service until Salesforce/Heroku assure us that they've completed work on their systems. Salesforce's most recent update, as of 9:38am PDT, is as follows: "Investigations are still ongoing. A permanent fix is in progress, and it will require disabling the configuration change that reintroduces impact."

9. monitoring Jun 10, 2025, 05:54 PM UTC

   We are seeing very little impact to our services currently, but Zipline's team will remain in an active alert state until we hear that a definitive fix has been deployed by Heroku/Salesforce. Salesforce are continuing to work on a permanent fix for their issues today. In their words: "We continue to work on the permanent fix and explore alternate paths to resolution. Once the fix is developed, an estimated time to resolution will be shared." We will pass on Salesforce's resolution ETA as soon as they state one.

10. monitoring Jun 10, 2025, 08:16 PM UTC

    We continue to see negligible impact to our services at this time, but Heroku have not yet indicated that they have fully resolved issues in their system, so we are continuing to monitor the situation closely. Salesforce/Heroku's most recent update, as of 12:46pm PDT, was as follows: "We are observing positive results in our initial testing on pre-production environments. We’re continuing to test the fix before applying it to production environments and will provide a resolution timeline once determined. We will provide another update within 30 minutes or sooner if new information becomes available."

11. monitoring Jun 10, 2025, 08:59 PM UTC

    Zipline systems continue to be minimally affected by Salesforce's troubles, and we have further altered our resource deployment so that we can better weather any continued issues overnight and into tomorrow. We continue to lack a firm resolution timeline from Salesforce. Their most recent update is as follows: "We don’t have additional information to share at this time. Our efforts remain focused on internal testing and validation as we continue to see incremental improvements. We will provide a resolution timeline as soon as possible, and we apologize for the continued trouble."

12. monitoring Jun 11, 2025, 03:00 AM UTC

    At present, Zipline is seeing little to no impact to our services from the ongoing daylong disruption to Salesforce/Heroku systems. Salesforce are continuing to work to stabilize their systems, and are currently initiating a fleetwide reboot of all machines across their Cloud services, including Heroku. It is possible that this may cause one or more brief service outages for Zipline overnight tonight, depending on if/when Salesforce reboot the clusters which house our application. Our on-call team remains ready to respond to any impacts overnight, and our Platform engineers will reassess the current state of play first thing tomorrow morning. Thank you for your patience as we weather someone else's storm together.

13. resolved Jun 11, 2025, 10:03 AM UTC

    Overnight, Heroku have announced that all further issues on their end have been resolved. We've seen no further impact from this incident overnight, and are therefore declaring it resolved.

Read the full incident report →

Started Apr 24, 2025, 08:23 PM UTC· resolved Apr 24, 2025, 11:36 PM UTC

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 →

Started Dec 12, 2024, 03:08 AM UTC· resolved Dec 12, 2024, 08:38 AM UTC

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 →