Expo API
performance benchmarks
Browse Expo's observed push API response time, error rates, and incident history over the last 90 days.
Live performance metrics
Real-world performance data from notifications sent through Knock.
| Message volume | Growth | Status page updates (30d) | Status page updates (90d) |
|---|---|---|---|
25M–100M | 2nd of 5 ↑ | 0 | 3 |
From August 15th to November 13th, Knock routed 25M–100M messages through Expo. For adoption, Expo ranks 2nd of 5 providers based on new channel connections, with adoption accelerating over the period. Expo reported 3 status page updates over the last 90 days, 0 of which were in the last 30 days.
Expo response time
Response time measures how long Expo takes to accept a push API request from Knock, including connection overhead and any automatic retries. Lower values mean faster notification hand-off.
| Median (p50) | p90 | p95 | p99 |
|---|---|---|---|
72ms | 99ms | 133ms | 535ms |
From August 15th to November 13th, Expo averaged a daily median response time (p50) of 72ms across all days in the range, meaning half of all push API requests on a typical day complete in under 72ms. The 99th percentile averaged 535ms, with a peak daily p99 of 1759ms. This is slightly higher than some providers, which may reflect additional processing Expo performs on notification acceptance.
Expo error rate
Error rate tracks the ratio of 5xx responses and timeouts to total push API requests. Knock automatically retries failed requests, so transient provider errors rarely affect end-user delivery.
| Avg. daily error rate | Highest daily rate | Peak error date | Zero-error days | Days above 0.01% |
|---|---|---|---|---|
0.02% | 0.51% | Oct 13 | 73 | 12 |
From August 15th to November 13th, Expo averaged a 0.02% daily error rate for 5xx responses and timeouts, with the highest single-day error rate reaching 0.51%. This is one of the lowest error rates among providers on Knock, indicating strong reliability and consistent uptime. Knock automatically retries failed requests, so transient provider errors rarely affect end-user delivery.
About these metrics: Data represents notifications sent through Knock to Expo during the specified period. Response time measures time from Knock to provider acceptance. Error rate includes only provider 5xx responses and timeouts.
Recent Expo incidents
Recent status page incidents for Expo
Started Oct 5, 2026 — Resolved Oct 5, 2026
This incident has been resolved.
Started Sep 8, 2026 — Resolved Sep 8, 2026
This incident has been resolved.
Started Sep 5, 2026 — Resolved Sep 5, 2026
This incident has been resolved.
Compare Expo with other providers
See how Expo compares on performance, reliability, and pricing.
About Expo
Expo provides a unified push notification API for React Native apps, abstracting away APNS and FCM complexity with free delivery and built-in receipt tracking.
Pros
- Simplifies push for React Native apps by abstracting away APNS and FCM complexity
- Free push notification delivery with no per-message costs
- Receipt tracking enables monitoring delivery success and debugging failures
- No need to manage platform-specific credentials or certificates
Cons
- Tied to the Expo ecosystem; apps ejected from Expo lose some push conveniences
- Platform features beyond push (EAS Build, EAS Update) require a paid plan at scale
- Adds a proxy layer between your app and APNS/FCM, which can increase latency
Frequently asked questions
Expo is a push notification provider commonly used for react native app notifications, cross-platform mobile messaging, real-time alerts and updates. Expo provides a unified push notification API for React Native apps, abstracting away APNS and FCM complexity with free delivery and built-in receipt tracking.
Expo push notification delivery is free at any volume. There is no per-notification charge. Expo limits sending to 600 notifications per second per project. Paid EAS plans cover builds, updates, and hosting, not push sends.
Based on real-world data from notifications sent through Knock, Expo accepts push API requests with a median response time of 72ms (p50) and 535ms at the 99th percentile.
From August 15th to November 13th, Expo showed an error rate of 0.02% for 5xx responses and timeouts across 25M–100M messages sent through Knock. Knock automatically retries failed requests, so transient provider errors rarely affect end-user delivery.
Key strengths include simplifies push for react native apps by abstracting away apns and fcm complexity and free push notification delivery with no per-message costs. On the other hand, tied to the expo ecosystem; apps ejected from expo lose some push conveniences and platform features beyond push (eas build, eas update) require a paid plan at scale.
Yes. Knock has a native Expo integration that enables you to send push notifications through Expo as part of a cross-channel workflow. You can combine Expo with other channels like in-app feeds, SMS, email, and Slack from a single API call.