Last checked: 48 seconds ago
Get notified about any outages, downtime or incidents for Adapty and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Adapty.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
API | Active |
Dashboard | Active |
View the latest incidents for Adapty and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Aug. 2, 2024, 2:30 p.m.
Description: We made an error with DNS records, which prevented all requests to the dashboard from being processed. This issue only affected the dashboard at [app.adapty.io](http://app.adapty.io); all APIs and SDKs worked normally, and there were no data losses. We're sorry about this incident.
Status: Postmortem
Impact: Major | Started At: July 31, 2024, 7:10 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: July 22, 2024, 9:12 p.m.
Description: Hello everyone! We had a networking issue with one of the main nodes. For some reason, the internal IP address associated with the node became inaccessible. The issue lasted from 11:37:30 to 11:41:00 UTC. It was resolved automatically without any fixes from our side, so we reached out to our infrastructure provider for details. The issue affected 12% of requests in the period, and due to its nature, we couldn't recreate them later since no requests were received by the server. Fallback paywalls worked as usual, and most requests will be retried automatically by SDK or Apple/Google servers. We're sorry about this and are considering ways to minimize the impact of such incidents.
Status: Postmortem
Impact: Minor | Started At: July 16, 2024, 11:37 a.m.
Description: Hello everyone! We had a networking issue with one of the main nodes. For some reason, the internal IP address associated with the node became inaccessible. The issue lasted from 11:37:30 to 11:41:00 UTC. It was resolved automatically without any fixes from our side, so we reached out to our infrastructure provider for details. The issue affected 12% of requests in the period, and due to its nature, we couldn't recreate them later since no requests were received by the server. Fallback paywalls worked as usual, and most requests will be retried automatically by SDK or Apple/Google servers. We're sorry about this and are considering ways to minimize the impact of such incidents.
Status: Postmortem
Impact: Minor | Started At: July 16, 2024, 11:37 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.