pingoru pingoru Fliplet had 14 outages in the last 2 years totaling 143h 41m of downtime, averaging 0.6 incidents per month.
There were 14 Fliplet outages since November 10, 2025 totaling 143h 41m of downtime. Each is summarised below. Incident details, duration, and resolution information.
Due to some unannounced changes by Apple to their API's, builds to the Apple App Store are currently non-functional. We are trying to get a resolution in place ASAP.
All resolved!
Fliplet suffered from a system outage which caused our US customers significant slow downs when using Studio and web apps on October 13th between 17:20 and 19:15 GMT. The issue has been caused by one of our databases in North California being heavily impacted by an unoptimised analytics query and its caching layer released as part of backend changes required to support Fliplet’s new app-based pricing offering earlier in the day.
Fliplet’s engineering team identified the root cause at 18:30 and turned off the feature by releasing a patch to staging environments shortly after for QA testing. At 19:00 the patch passed QA testing and was released to production environments as a hotfix within 10 minutes. At 19:15, internal and external monitors reported all systems back to normal.
Currently we are seeing some slowness in the time to execute native app builds. We hope to see this resolve it self in due course.
Native app builds have returned to normal performance
Logging in on Fliplet Studio is currently unavailable due to an issue with our authentication systems.
We expect the authentication system to be working back again within the next 10 minutes.
The issue with the login system has now been resolved. Please reload Fliplet Studio on your browser to log back in.
An issue occurred during a deployment causing sign ins to fail, revert in process
Revert completed
Apple have made some changes to their APIs which has had a knock-on effect of our services. Certain conditions may cause builds to fail.
We have found the root cause and are putting together some guides to get around the issue.
engineers are creating a release to support the work around
A fix has been released allowing repeat builds to succeed A fix has been released allowing 1st time builds to be submitted caveat - studio will still show the 1st time build as failed, however it did succeed. Fix for studio to correctly display success status is being worked on
studio updated to support new messaging of iOS build status
Between the following hours there will be degraded/intermittent service for publishing your iOS app builds. If you continue to experience issues with our service outside of the hours, don't hesitate to reach out to our support team. 24 April 2024 02:00 UTC → 10:00 UTC 14:00 UTC → 22:00 UTC
brownout period has passed and normal operations resumed
We are experiencing issues with our EU email server. You may have trouble accessing apps that require email verification and emails sent from Fliplet Apps and Studio via integrations, components, Communicate JS APIs and Data Source Hooks might be affected as well. Our administration and engineering teams are investigating the issue and will report back with an update as soon as possible.
We have identified the root cause of the issue and our email provider is looking into it.
The service is now resumed. Emails that have not been sent yet will be received throughout the day.
We're currently experiencing some internal server issues that are causing outages on our system for EU customers. Fliplet Studio and any apps are currently affected.
The issue has been resolved and all services are back online
AWS SES Resolved
Outbound emails sent from Fliplet Apps and Studio via integrations, components, Communicate JS APIs and Data Source Hooks are currently on hold due to an issue with our Email provider.
Our administration and engineering teams are investigating the issue and will report back with an update as soon as possible.
Emails have resumed to be sent, although we're still not able to deliver queued emails that have not been sent in the past few hours due to the email provider issue. We will update you as soon as we have news on the pending emails that are still to be sent.
We're once again experiencing issues with sending emails and we're looking into our alternatives for sending emails. We should be able to provide an update soon.
Some of the emails that have been sent throughout the day are still queued on our previous provider and we will be working hard to retrieve those emails and deliver them to the target recipients using the new service that we're in the middle of implementing. Please get in touch with our customer support team for more details or if you need further help.
We have managed to restore partial service, however we are still being heavily limited. This means emails may continue to be held and delayed.
We have fully restored email services and migrate to a different provider.
We have received reports of AWS suffering from widespread Internet connectivity issues in their US (North California) data centers. AWS Official statement: [07:52 AM PST] We are investigating Internet connectivity issues to the US-WEST-1 Region.
AWS: [08:01 AM PST] We have identified the root cause of the Internet connectivity to the US-WEST-1 Region and have taken steps to restore connectivity. We have seen some improvement to Internet connectivity in the last few minutes but continue to work towards full recovery.
AWS: 8:10 AM PST We have resolved the issue affecting Internet connectivity to the US-WEST-1 Region. Connectivity within the region was not affected by this event. The issue has been resolved and the service is operating normally.
Native Apps (iOS and Android) and Web Apps went down.
Integrations (Data Sources) went down.
Canada and USA went down.
Native Apps (iOS and Android) and Web Apps recovered.
Canada, USA, and Integrations (Data Sources) recovered.
Fliplet Studio is unavailable due a faulty deployment.
Fliplet Studio is back inline.