Manifest CDN throttle/limitation

Please provide the following:

  1. SDK Version: 41.0.0
  2. Platforms(Android/iOS/web/all): Android / iOS
  3. Add the appropriate “Tag” based on what Expo library you have a question on.

We are doing some load testing and experienced an error when the manifest is fetched from the CDN. I am wondering if there are any throttle / limitations to the CDN that Expo uses on the AWS/GCP side?

Normally, when over-the-air (OTA) updates are enabled, your app will fetch updates comprising JavaScript bundles and assets from Expo’s CDN. However, there will be situations when you will want to host your JS bundles and assets on your own servers. For example, OTA updates are slow or unusable in countries that have blocked Expo’s CDN providers on AWS and Google Cloud.

The test is about 1000 instances within 2 minutes fired off the same ip address.

[expo.io/104.197.216.164] failed: Connection refused (Connection refused)

The updates server is intended for typical end-user behavior. Someone might cold launch an app a few times a day, and rarely a few times within a minute. Abnormal behavior would be checking for an update dozens of times a day of times a day. Checking for an update every hour is acceptable.

We don’t have an explicit throttling policy but prioritize the health of the service. This may result in throttling or IP blocks against clients that are hurting others.

We don’t think it’s normal but apps that check excessively often should build their own service that tells apps when they should check the Expo service for a new update. Most developers never need to think about this, though.