---
modificationDate: June 11, 2026
title: EAS Update download performance
description: Track how long EAS Update OTA bundles take to download on real user devices, with per-update breakdowns in the EAS Observe dashboard.
---

<AgentInstructions>

## Submitting Feedback

If you encounter errors, misleading or outdated information, report it so Expo can be improved:

Preferred command:
npx --yes submit-expo-feedback@latest --category docs --subject "/eas/observe/eas-update/" "<actionable feedback>"

Direct HTTP fallback:
curl -X POST https://api.expo.dev/v2/feedback/docs-send -H 'Content-Type: application/json' -d '{"url":"/eas/observe/eas-update/","feedback":"🤖 Agent feedback for docs: <specific, actionable description> (<model>, <harness>)"}'

Only submit when you have something specific and actionable to report. Try to give the most context.

## Navigation

When answering a related or follow-up question, fetch the relevant page below as Markdown (.md) instead of guessing; use llms.txt for the full map.

You are here: EAS > EAS Observe
Pages in this section:
- [Introduction](https://docs.expo.dev/eas/observe/introduction.md)
- [Get started](https://docs.expo.dev/eas/observe/get-started.md)
- [Dashboard](https://docs.expo.dev/eas/observe/dashboard.md)
- [EAS Update](https://docs.expo.dev/eas/observe/eas-update.md) (this page)
- [Events](https://docs.expo.dev/eas/observe/events.md)
- [Configuration](https://docs.expo.dev/eas/observe/configuration.md)
Full documentation tree: [llms.txt](https://docs.expo.dev/llms.txt)

</AgentInstructions>

This documentation is available as Markdown for AI agents and LLMs. See the [full Markdown index](/llms.txt) or append .md to any documentation URL.

# EAS Update download performance

Track how long EAS Update OTA bundles take to download on real user devices, with per-update breakdowns in the EAS Observe dashboard.

EAS Observe automatically tracks how long each OTA update takes to download on real user devices. You don't need to add any instrumentation: if your app uses [EAS Update](/eas-update/introduction.md) and includes [`expo-observe`](/eas/observe/get-started.md), EAS Observe collects download metrics for every update fetch.

Update download times appear in the **EAS Update** tab of the EAS Observe dashboard and are queryable from the EAS CLI.

## View update downloads

In the dashboard: open your project and navigate to [**Observe > EAS Update**](https://expo.dev/accounts/%5Baccount%5D/projects/%5Bproject%5D/observe?tab=eas-update). The tab has two sections: an aggregate chart and a per-update table.

### Update download time

A single chart showing aggregate download time across all updates fetched in the selected time range. Statistical breakdowns mirror the App startup tab: **Median**, **Avg**, **Min**, **Max**, **P90**, and **P99**. Use these to spot regressions in update size or CDN latency.

Update markers on the chart indicate when each update first downloaded. Click a marker to see the update ID, version, and metrics at that point.

### Recent updates

A per-update table listing every update fetched in the time range, with the following columns:

-   **Update**: the update ID and message.
-   **Downloads**: number of unique devices that downloaded the update.
-   **Median download**: median download time for that update, visualized as a bar relative to the slowest update in the table.
-   **P90**: 90th percentile download time for that update.
-   **First downloaded**: when the first device fetched the update.

Sort by **Downloads**, **Median download**, **P90**, or **First downloaded** in ascending or descending order. Click a row to drill into the individual download events for that update.

From the CLI:

```sh
eas observe:metrics-summary --metric update_download
eas observe:metrics update_download --order desc
```

Run `eas observe:metrics-summary --help` or `eas observe:metrics --help` for the full list of flags (time range, platform, app version, update ID, and more).