OneSignal
performance benchmarks
Browse OneSignal'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) |
|---|---|---|---|
1M–10M | 5th of 5 → | 8 | 18 |
From April 14th to July 13th, Knock routed 1M–10M messages through OneSignal. For adoption, OneSignal ranks 5th of 5 providers based on new channel connections, with adoption holding steady over the period. OneSignal reported 18 status page updates over the last 90 days, 8 of which were in the last 30 days.
Response time
Response time measures how long OneSignal 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 |
|---|---|---|---|
209ms | 320ms | 460ms | 1138ms |
From April 14th to July 13th, OneSignal averaged a daily median response time (p50) of 209ms across all days in the range, meaning half of all push API requests on a typical day complete in under 209ms. The 99th percentile averaged 1138ms, with a peak daily p99 of 2714ms. This is slightly higher than some providers, which may reflect additional processing OneSignal performs on notification acceptance.
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% | 1.00% | May 19 | 82 | 5 |
From April 14th to July 13th, OneSignal averaged a 0.02% daily error rate for 5xx responses and timeouts, with the highest single-day error rate reaching 1.00%. 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 OneSignal during the specified period. Response time measures time from Knock to provider acceptance. Error rate includes only provider 5xx responses and timeouts.
Recent OneSignal incidents
Recent status page incidents for OneSignal
Started Jul 6, 2026 — Resolved Jul 6, 2026
Status: Resolved The issue has been resolved. All impacted systems are now operating normally. Affected components Integrations (Operational)
Started Jul 1, 2026 — Resolved Jul 1, 2026
Status: Resolved The issue has been resolved. All impacted systems are now operating normally. Affected components Journeys (Operational)
Started Jun 26, 2026 — Resolved Jun 26, 2026
Status: Complete Maintenance has been completed. Affected components Analytics & Reporting (Operational)
Started Jun 25, 2026 — Resolved Jun 25, 2026
Status: Resolved The issue has been resolved. All impacted systems are now operating normally. The analytic lag is totally processed. Affected components Analytics & Reporting (Operational)
Started Jun 23, 2026 — Resolved Jun 23, 2026
Status: Complete All maintenance tasks are complete. Services should be back to normal. Affected components Dashboard / UI (Operational) APIs & SDK Endpoints (Operational) Journeys (Operational)
About OneSignal
OneSignal is a cross-platform push notification service with built-in segmentation, A/B testing, analytics, and intelligent delivery optimization.
Pros
- Generous free tier with unlimited mobile push makes it accessible for small teams and hobby projects
- Visual editor and prebuilt UI enable non-technical teammates to compose, target, and schedule campaigns
- Broad channel coverage including push, email, SMS, and in-app messages from a single platform
- Fast to get started with SDKs, guided setup, and strong documentation
Cons
- Workflow builder is tuned for marketing campaigns and lacks granular, event-driven control for transactional product messaging
- Subscription and tag-based preferences model is less flexible than a user-and-channel preference model for complex cross-channel logic
- Separated environments for development, staging, and production aren't first-class, which can complicate team workflows
- End-to-end observability and message-level debugging is more limited than dedicated notification infrastructure platforms
Frequently asked questions
What is OneSignal?
OneSignal is a push notification provider commonly used for cross-platform mobile push notifications, web push notifications, engagement campaigns with a/b testing. OneSignal is a cross-platform push notification service with built-in segmentation, A/B testing, analytics, and intelligent delivery optimization.
How much does OneSignal cost?
OneSignal offers a free tier for up to 10,000 subscribers. Growth plans start at $9/month with additional subscribers and features. Professional plans start at $99/month with advanced analytics, in-app messaging, and journeys. Enterprise pricing is custom. OneSignal does not offer a permanent free tier.
How fast is OneSignal?
Based on real-world data from notifications sent through Knock, OneSignal accepts push API requests with a median response time of 209ms (p50) and 1138ms at the 99th percentile.
How reliable is OneSignal?
From April 14th to July 13th, OneSignal showed an error rate of 0.02% for 5xx responses and timeouts across 1M–10M messages sent through Knock. Knock automatically retries failed requests, so transient provider errors rarely affect end-user delivery.
What are the pros and cons of OneSignal?
Key strengths include generous free tier with unlimited mobile push makes it accessible for small teams and hobby projects and visual editor and prebuilt ui enable non-technical teammates to compose, target, and schedule campaigns. On the other hand, workflow builder is tuned for marketing campaigns and lacks granular, event-driven control for transactional product messaging and subscription and tag-based preferences model is less flexible than a user-and-channel preference model for complex cross-channel logic.
Does OneSignal work with Knock?
Yes. Knock has a native OneSignal integration that enables you to send push notifications through OneSignal as part of a cross-channel workflow. You can combine OneSignal with other channels like in-app feeds, SMS, email, and Slack from a single API call.
Use OneSignal with Knock
Knock enables you to integrate OneSignal alongside other notification channels, manage templates, and orchestrate cross-channel workflows from a single platform.