Push API benchmarks
Real-time performance, reliability, and uptime benchmarks for top push notification providers, powered by proprietary data from millions of notifications sent through Knock.
Performance at a glance
Sort and filter push notification providers by response time, error rate, and growth.
| Provider | Message volume | Median response time | Error rate | Growth |
|---|---|---|---|---|
 | 25M–100M | 42ms | 0.20% | 2nd |
 | 25M–100M | 59ms | 0.00% | 3rd |
 | 25M–100M | 79ms | 0.03% | 1st |
 | <1M | 225ms | 0.13% | 4th |
Compare providers
Pick any two providers for a head-to-head comparison of performance, reliability, and pricing.
| Provider | Volume | Median response time | Error rate | Growth |
|---|---|---|---|---|
| Apple Push (APNS) | 25M–100M | 59ms | 0.00% | 3rd ↓ |
| Firebase FCM | 25M–100M | 79ms | 0.03% | 1st → |
Explore provider benchmarks
Explore detailed performance benchmarks, feature comparisons, and pricing for each push notification provider.
Our methodology
How we collect, measure, and present the data behind these benchmarks.
Time range
All metrics reflect a trailing 90-day window. Point-in-time load tests don't capture the variability of a production system handling thousands to millions of requests daily, so we use a longer window to surface the effects of system congestion and public incidents without penalizing providers that are actively improving.
Notification volume
Volume represents the total number of sampled push API requests routed through Knock during the period. Because Knock is an orchestration layer, we cannot influence the sending patterns of our customers, so volume varies by provider. To normalize for this, we group providers into volume bands that indicate how statistically confident we are in the observed metrics. Providers with low volume are flagged so you can weigh the results accordingly.
Response time
Response time is measured as the elapsed time from when Knock sends an API request to when the provider returns a response indicating notification acceptance. This measures API acceptance latency rather than end-to-end delivery speed, since push delivery confirmation varies by platform. We compute percentiles (p50, p90, p95, p99) using exact quantile functions. The measurement includes HTTP connection pooling time and network latency, applied consistently across all providers.
Error rate
Error rate is the ratio of requests that received a 5xx status code to total requests for the period. Knock automatically retries failed requests, so a single request can produce multiple error entries if each retry also fails. We believe this accurately represents the provider's availability during those periods.
Channel growth
In Knock, a connection to a provider API is modeled as a channel. Growth rank reflects how many new channels were created for each provider during the 90-day window. To detect directional trends, we split the window into two 45-day halves and compare them, producing the trend indicators (up, down, or stable) shown alongside each rank.
Frequently asked questions
Which push notification provider has the lowest API response time?
Based on real-world data from 100M–500M notifications sent through Knock from January 22nd to April 22nd, Expo has the lowest median API response time at 42ms (p50). The top three by response time are Expo (42ms), Apple Push (APNS) (59ms), Firebase FCM (79ms).
Which push notification provider is the most reliable?
Apple Push (APNS) currently has the lowest error rate at 0.00% for 5xx responses and timeouts. The top three by reliability are Apple Push (APNS) (0.00%), Firebase FCM (0.03%), and OneSignal (0.13%). Knock automatically retries failed requests across all providers.
Which push notification provider is the most popular?
By volume on the Knock platform, Expo leads with 25M–100M notifications from January 22nd to April 22nd. The top three by volume are Expo (25M–100M), Apple Push (APNS) (25M–100M), Firebase FCM (25M–100M).
Which push notification provider is growing the fastest?
Firebase FCM currently ranks 1st in growth among 4 providers tracked on the Knock platform. The top three fastest-growing providers are Firebase FCM, Expo, Apple Push (APNS).
Can I use multiple push notification providers with Knock?
Yes. Knock enables you to integrate any combination of push notification providers into a single notification workflow. You can route between providers, run migrations, or use different providers for different platforms, all without changing your application code.
Use any of these providers with Knock
Knock enables you to integrate any combination of push notification providers into a single notification workflow. Manage templates, orchestrate cross-channel delivery, and switch providers without changing your code.