Apple Push (APNS) vs Firebase FCM
Compare Apple Push (APNS) and Firebase FCM based on observed push API performance and features
Live performance comparison
Real-world performance data from notifications sent through Knock
| Provider | Notification volume | Growth | Status page updates (30d) | Status page updates (90d) |
|---|---|---|---|---|
| 25M–100M | 3rd of 5 ↓ | 0 | 0 |
| 25M–100M | 1st of 5 → | 0 | 2 |
From January 22nd to April 22nd, Knock routed 25M–100M notifications through Apple Push (APNS) and 25M–100M through Firebase FCM. Apple Push (APNS) reported 0 status page updates over the last 90 days, while Firebase FCM reported 2.
Response time
Response time measures how long each provider takes to accept a push API request from Knock, including connection overhead and any automatic retries. Lower values mean faster notification hand-off.
| Provider | Median (p50) | p90 | p95 | p99 |
|---|---|---|---|---|
| 59ms | 101ms | 117ms | 153ms |
| 79ms | 149ms | 171ms | 296ms |
The chart above shows each provider's daily median response time (p50) from January 22nd to April 22nd. The top-line number is an average of these daily values: Apple Push (APNS) averaged 59ms compared to 79ms for Firebase FCM. Apple Push (APNS)'s highest daily p50 was 69ms; Firebase FCM's was 97ms. Apple Push (APNS) is 20ms faster at the median, which can add up at high volumes.
The 90th percentile (p90) captures the slowest 10% of requests, revealing how each provider handles moderate stress. Averaged across all days, Apple Push (APNS) has a p90 of 101ms compared to 149ms for Firebase FCM. The highest daily p90 was 135ms for Apple Push (APNS) and 158ms for Firebase FCM. Apple Push (APNS) handles these slower requests 48ms faster, suggesting more consistent performance across the board.
The 99th percentile (p99) represents the long tail — the slowest 1% of requests. Averaged across all days, Apple Push (APNS) reached 153ms at p99 while Firebase FCM reached 296ms. The highest daily p99 was 293ms for Apple Push (APNS) and 350ms for Firebase FCM, indicating the worst-case response time during spikes or provider-side congestion. Apple Push (APNS) shows a tighter tail, which may matter for time-sensitive push notifications like real-time alerts where even rare delays can impact user experience.
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.
| Provider | Avg. daily error rate | Highest daily rate | Peak error date | Zero-error days | Days above 0.01% |
|---|---|---|---|---|---|
| 0.00% | 0.00% | Jan 22 | 91 | 0 |
| 0.03% | 0.08% | Feb 3 | 13 | 56 |
Averaged across the date range, Apple Push (APNS) shows a 0.00% daily error rate compared to 0.03% for Firebase FCM. The highest single-day error rate was 0.00% for Apple Push (APNS) and 0.08% for Firebase FCM. Both providers show similar reliability levels, with error rates well within acceptable thresholds. Knock automatically retries failed requests to both providers, minimizing the impact of transient errors on end-user delivery.
About these metrics: Data represents notifications sent through Knock during the specified period. Response time measures time from Knock to provider acceptance. Error rate includes only provider 5xx responses and timeouts.
Recent Apple Push (APNS) incidents
Recent status page incidents for Apple Push (APNS)
No incidents reported in the last 90 days
Recent Firebase FCM incidents
Recent status page incidents for Firebase FCM
Started Mar 17, 2026 — Resolved Mar 17, 2026
404 error for Firebase Cloud Messaging clients sending to a URL with a trailing slash
Started Mar 8, 2026 — Resolved Mar 31, 2026
Minor Intermittent Latency Increases for Some Firebase Cloud Messaging Services
Pros and cons
Apple Push (APNS)
Firebase FCM
Pros
- Free with no per-notification cost at any volume
- Native platform integration ensures the most reliable delivery to Apple devices
- Supports rich notifications with media, interactive elements, and Live Activities
- Token-based auth simplifies certificate management at scale
Pros
- Free with no per-notification cost at any volume
- Cross-platform support for Android, iOS, and web from a single API
- Deep integration with the Firebase ecosystem including analytics and remote config
- Topic and device group messaging simplifies broadcasting to subscriber segments
Cons
- Limited to Apple platforms only (iOS, macOS, watchOS, tvOS)
- No built-in analytics or delivery confirmation beyond basic device feedback
- Apple's status page has no public API or RSS feed for incident monitoring
Cons
- iOS delivery still routes through APNS, adding a layer of indirection
- Payload size limited to 4KB, which can be restrictive for rich content
- Firebase console UI can be complex for teams not already using Firebase
Frequently asked questions
What is the difference between Apple Push (APNS) and Firebase FCM?
APNS is Apple's native push notification service, providing free, reliable delivery to all Apple devices with support for rich media and Live Activities. Firebase Cloud Messaging (FCM) is Google's free, cross-platform push notification service supporting Android, iOS, and web with topic messaging and analytics integration. Apple Push (APNS) is best suited for ios and macos notifications, while Firebase FCM is geared toward cross-platform android and web notifications.
Which is cheaper, Apple Push (APNS) or Firebase FCM?
APNS is free to use with no per-notification cost. Apple does not charge for push notification delivery regardless of volume. The only requirement is an active Apple Developer Program membership ($99/year). Firebase Cloud Messaging is free to use with no per-notification cost. Google does not charge for message delivery regardless of volume. FCM is included in all Firebase plans, including the free Spark plan. The best value depends on your sending volume and target platforms.
Which is faster, Apple Push (APNS) or Firebase FCM?
Based on real-world data from Knock, Apple Push (APNS) has a median push API response time (p50) of 59ms compared to 79ms for Firebase FCM.
Which is more reliable, Apple Push (APNS) or Firebase FCM?
From January 22nd to April 22nd, Apple Push (APNS) showed an error rate of 0.00% while Firebase FCM showed 0.03%. Both rates are within acceptable thresholds for production push notification delivery, and Knock automatically retries failed requests to minimize the impact of transient errors.
Which is more popular, Apple Push (APNS) or Firebase FCM?
On the Knock platform, Apple Push (APNS) handled 25M–100M notifications from January 22nd to April 22nd compared to 25M–100M for Firebase FCM. Apple Push (APNS) is currently seeing declining volume, while Firebase FCM volume has remained stable.
Can I use both Apple Push (APNS) and Firebase FCM together?
Yes. Knock enables you to integrate multiple push notification providers into a single notification workflow. You can use Apple Push (APNS) and Firebase FCM side by side, route traffic between them, or migrate from one to the other without changing your application code.
What are the main pros and cons of Apple Push (APNS) vs Firebase FCM?
Apple Push (APNS) strengths include free with no per-notification cost at any volume and native platform integration ensures the most reliable delivery to apple devices. Firebase FCM strengths include free with no per-notification cost at any volume and cross-platform support for android, ios, and web from a single api. On the other hand, Apple Push (APNS) drawbacks include limited to apple platforms only (ios, macos, watchos, tvos), while Firebase FCM drawbacks include ios delivery still routes through apns, adding a layer of indirection.
Use either provider with Knock
Knock enables you to integrate Apple Push (APNS), Firebase FCM, or any combination of push notification providers into a single notification workflow. Manage templates, orchestrate cross-channel delivery, and switch providers without changing your code.