Adapty had 27 outages in the last 2 years totaling 25h 21m of downtime — averaging 1.1 incidents per month.
There were 27 Adapty outages since April 19, 2025 totaling 25h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.
We’re observing a drop of the rate in Google Play pub-sub notifications. You may notice delay in the delivery of events. We are investigating.
This incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating elevated error rates on the EU API endpoint (api-eu.adapty.io) caused by a hardware failure at our hosting provider. SDK requests to the EU region may fail or be retried. Data will be delivered once the service is restored. We will post an update within 30 minutes.
We have identified the cause: a hardware failure at our hosting provider affected the primary database server and several nodes in the EU region. SDK API requests to the EU endpoint (api-eu.adapty.io) are currently failing. Our team, together with the provider, is working on restoring the service by switching to the standby database. No purchase data is lost: SDK requests are retried automatically and events will be processed once the service is restored. Next update in 30 minutes.
The EU API (api-eu.adapty.io) has been fully operational since 08:16 UTC after we failed over to the standby database. Error rates have been at zero since 08:24 UTC. Background processing (events, integrations, analytics) is catching up on the backlog accumulated during the outage, so some events in the dashboard and integrations may appear with a delay. We are monitoring closely and will post a final update once processing is back to normal
This incident has been resolved. All systems are operating normally.
Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. No data has been lost and the system should be caught up shortly.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We're experiencing an increased response time for the SDK API requests and are currently looking into the issue
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have deployed a fix for an issue that prevented approximately 160 accounts from signing in to the dashboard. SDK and event processing have been operating normally throughout the incident — only dashboard sign-in for the affected accounts was impacted. We are now monitoring application logs to confirm the fix is fully resolving the issue, and will post another update shortly.
Monitoring has confirmed that the errors are no longer occurring. All previously affected accounts are able to sign in to the dashboard normally. SDK and event processing were unaffected throughout the incident. Marking this incident as resolved. Thank you for your patience.
We’re currently experiencing delays in event processing, which may affect third-party integrations, as well as transaction processing for Paddle and Stripe. No data has been lost, and all events will be delivered. We apologize for the inconvenience and appreciate your patience.
Root cause has been identified and fix was deployed
We are currently experiencing issues with push notification delivery through our OneSignal integration. This is caused by an ongoing incident on OneSignal's side affecting their Dashboard/UI and API & SDK Endpoints. OneSignal has identified the root cause and is working towards a resolution. You can track their incident status at https://status.onesignal.com/
The issue with push notification delivery via OneSignal has been resolved. Event processing is operating normally. The root cause was an outage on OneSignal's side affecting their Dashboard and API endpoints. which has now been fixed by their team. No action is required on your end. If you notice any remaining delays, please contact our support team.
We're experiencing an increased response time for the SDK API requests and are currently looking into the issue
Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. No data has been lost and the system should be caught up shortly.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Since March 5 at 2:00 PM GMT, Facebook's API for handling mobile app events has been timing out. This is affecting their Ads Creation and Editing API; Meta has acknowledged the outage on their status page - https://metastatus.com/marketing-api . The good news: things are recovering. Successful requests are climbing back up, and all your events will come through — just a bit later than usual. We'll keep an eye on it. Thanks for your patience! — Adapty Infrastructure Team
Events processing returned to normal.
We're experiencing an elevated level of API errors and are currently looking into the issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
As a result of the release, Adapty’s subscription plan assignment was impacted. A small portion of customers could not receive their updated plan and also experienced issues accessing the Dashboard
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
SDK API affected and failing to handle majority of the requests
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
Both SDK and Dashboard API are back to normal. We're waiting for the event queue to empty.
This incident has been resolved.
We are currently experiencing issues sending profile events exports to AWS S3 and Google Cloud. We expect to restore normal operation within the next two hours. After that, we will run all scheduled export jobs that were missed during the incident. This issue does not affect the normal operation of the service or data collection—only the delivery of exports is delayed.
Profile events exports to AWS S3 and Google Cloud are back to normal, and all pending export jobs have been processed. All event exports have been delivered to customers.
We are currently experiencing an issue with webhook delivery. Some webhook events are being delayed or not delivered as expected. As a result, customers may observe a reduced number of webhook events, including subscription and access level updates. This may impact subscription approvals and credit processing. Our engineering team is actively investigating the root cause and working to restore normal delivery.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
From 06:20 to 07:00 UTC, subscription purchase events WEB hooks haven't been sent to subscribers. During the next 3h, right after the incident ended, all delayed events were delivered successfully.
We are currently investigating this issue.
A fix has been implemented, and we are monitoring the results
This incident has been resolved.
We're experiencing an increased response time for the dashboard and API requests and are currently looking into the issue.
We are currently seeing elevated errors and degraded performance for requests routed through Cloudflare in the UK region. Our team is investigating the issue. Cloudflare has acknowledged related network problems on their status page, and we are monitoring their updates while continuing to assess the impact on our services.
This incident has been resolved.
From 12:05 UTC to 15:09 UTC on November 6, Adapty experienced intermittent network issues that resulted in approximately 7% of requests being retried. Unfortunately, this event was not automatically surfaced by our internal monitoring, and our external monitoring did not trigger an alert because it only reports after two consecutive failures. As a result, we did not notify customers in a timely manner. The underlying issue has been mitigated, and systems are operating normally. We are currently implementing an additional monitoring layer to collect status codes directly from the CDN providers we use, ensuring faster and more accurate detection in the future. We’re sorry for the disruption and for not alerting you sooner. We are taking steps to ensure better visibility and responsiveness going forward.