Is Adapty down?
Last checked 1m agoNo incidents right now.
Adapty is operational right now. Last checked 1m ago; the most recent incident resolved 4d ago.
Real-time Adapty status, recent outages, and incident history: pulled directly from Adapty's official status page at status.adapty.io every 5 minutes. Pingoru tracks 4 Adapty services and has captured 13 incidents in the last 90 days (95.00% uptime). Get email, Slack, Discord, or webhook alerts the moment Adapty reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- APIDashboardEventsEU region
Timeline · 4 updates
- identified · Oct 03, 2026, 01:57 AM UTC
We're experiencing an increased response time for the SDK API requests and are currently looking into the issue
- identified · Oct 03, 2026, 02:11 AM UTC
We are continuing to work on a fix for this issue.
- resolved · Oct 03, 2026, 02:59 AM UTC
This incident has been resolved.
- postmortem · Oct 03, 2026, 04:28 PM UTC
Duration: October 2, 23:46 UTC to October 3, 02:54 UTC \(3 hours 8 minutes\) Affected: SDK API, server-side API and web API in the US region. The Adapty Dashboard and the EU region were not affected. We're sorry for the disruption this caused you and your users. We know how much you rely on Adapty, and we let you down. **What happened** At 23:46 UTC, a network switch at our hosting provider's data center had a disruption lasting about one second. Because of it, one of the servers in our US profile database briefly lost connection to the rest of the cluster and then reconnected. When a server rejoins like this, the database redistributes and re-syncs data across the whole cluster to make sure every copy is up to date. While that re-sync was running, one type of lookup failed: finding a profile by customer user ID or device. The SDK relies on this lookup to create new profiles and identify users. Until the re-sync finished at 02:54 UTC, about 30% of SDK requests returned errors, and many of the rest responded more slowly than usual. During the same window, about 90% of server-side API requests failed. Errors stopped once the re-sync completed. **How it affected apps** Profile creation failed when a customer user ID was used. New users opening an app often couldn't do it. Apps that wait for profile creation before showing a paywall were affected the most. For these apps, the paywall often didn't load, so some users couldn't make a purchase. Apps that let purchases go ahead without waiting for profile creation were much less affected. Purchases went through, but some profile data, such as attribution, may be missing for users affected during the incident. **What we're doing next** The lookup that failed should never have been able to take down critical SDK requests like these. We're working on a permanent fix that removes this dependency, so the main SDK paths, including profile creation and paywalls, keep working normally even while the database is re-syncing. Once again, we're truly sorry this happened.
Latest: Duration: October 2, 23:46 UTC to October 3, 02:54 UTC \(3 hours 8 minutes\) Affected: SDK API, server-side API and web API in the US region. The Adapty Dashboard and the EU region…
-
- Events
Timeline · 2 updates
- identified · Sep 16, 2026, 05:32 PM UTC
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.
- resolved · Sep 16, 2026, 05:56 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- APIDashboardEventsEU region
Timeline · 7 updates
- identified · Sep 15, 2026, 01:43 PM UTC
We're experiencing an elevated level of API errors and are currently looking into the issue.
- identified · Sep 15, 2026, 02:06 PM UTC
We are continuing to work on a fix for this issue.
- identified · Sep 15, 2026, 02:23 PM UTC
We are continuing to work on a fix for this issue.
- identified · Sep 15, 2026, 02:33 PM UTC
We are continuing to work on a fix for this issue.
- identified · Sep 15, 2026, 02:43 PM UTC
We are continuing to work on a fix for this issue.
- monitoring · Sep 15, 2026, 02:46 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Sep 15, 2026, 04:23 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- APIDashboardEvents
Timeline · 4 updates
- investigating · Sep 10, 2026, 07:04 AM UTC
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.
- identified · Sep 10, 2026, 07:53 AM UTC
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.
- monitoring · Sep 10, 2026, 08:35 AM UTC
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
- resolved · Sep 10, 2026, 10:08 AM UTC
This incident has been resolved. All systems are operating normally.
Latest: This incident has been resolved. All systems are operating normally.
-
- Events
Timeline · 3 updates
- identified · Sep 01, 2026, 02:07 PM UTC
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.
- monitoring · Sep 01, 2026, 04:51 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Sep 01, 2026, 05:23 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
Incident record
Since April 2026 · Statuspage by Atlassian · 4 components checked every 5 minutesThe longest incident in the last year, Dashboard Service Disruption on February 16, 2026, ran for 12 hours. 18 maintenance windows announced in the same period.
Most affected components, last 12 months
- API23
- Dashboard22
- Events15
- EU region2
Latest incidents
- Increased response time on mobile SDK API
We're experiencing an increased response time for the SDK API requests and are currently looking into the issue
- Google Play pub-sub notifications problem
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.
- Elevated API Errors in EU region
We're experiencing an elevated level of API errors and are currently looking into the issue.
- Started Oct 02, 2026, 11:46 PM UTC · Resolved Oct 03, 2026, 02:54 AM UTC · 3h 8m
- Started Sep 16, 2026, 05:32 PM UTC · Resolved Sep 16, 2026, 05:56 PM UTC · 23m
- Elevated API Errors in EU region ResolvedStarted Sep 15, 2026, 01:43 PM UTC · Resolved Sep 15, 2026, 04:23 PM UTC · 2h 40m
- Elevated API errors (EU region) ResolvedStarted Sep 10, 2026, 07:04 AM UTC · Resolved Sep 10, 2026, 10:08 AM UTC · 3h 3m
- Started Sep 01, 2026, 02:07 PM UTC · Resolved Sep 01, 2026, 05:23 PM UTC · 3h 16m