Fillout had 18 outages in the last 2 years totaling 20h 47m of downtime — averaging 0.7 incidents per month.
There were 18 Fillout outages since July 15, 2025 totaling 20h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We believe the issue is isolated to apps with "OpenAI/Claude" integrations, our team is investigating.
The issue has been identified and a fix is being implemented.
The incident has been resolved, apps using the OpenAI/Claude connector are fully operational again. Our team is assessing the root cause to mitigate risk going forward.
We are currently investigating this issue.
We are continuing to investigate this issue.
Our team has implemented a fix and is monitoring the result.
We are continuing to monitor for any further issues.
The incident has been resolved. We are investigating the root cause and will be making infrastructure improvements to reduce the chance of this happening again.
We are currently investigating this issue.
Our main infrastructure provider has reported an outage. We are working with them to get a resolution ASAP.
Our infrastructure provider has identified the issue and is implementing a fix.
A fix has been implemented and we are monitoring the results.
We had an outage with one of our infrastructure providers that impacted Zite and Fillout from 1:41 to 2:32 UTC. The issue has now been resolved, and our team is continuing to monitor things closely. We're also doing a deeper review to understand the root cause, what we could have caught sooner, and how we can reduce the chance of this happening again. We'll continue posting updates on this status page if they occur. We're very sorry for the disruption. Please ping our team at [email protected] if you have any questions, we're here to help.
We are currently investigating this issue.
Our team has identified the cause and is working on a fix. Certain published Zite apps are also experiencing slowness.
A fix has been implemented and we are monitoring the results.
This incident has been resolved and service is operating normally again. We’re continuing to review the root cause and identify improvements to help prevent similar issues in the future.
Due to an earlier issue, certain Airtable connections may have been automatically disconnected by Airtable. Please check https://build.fillout.com/home/settings/integrations and click “Reconnect” on your Airtable connections if they are marked as disconnected. Contact [email protected] with any questions, we are here to help. Thank you and apologies for the inconvenience.
We are also investigating issues reconnecting certain Google Calendar connections to Fillout Scheduling
Connections to services like Airtable and Google Calendar should now reconnect automatically. Our engineering team is investigating the root cause and working to reduce the likelihood of this happening again. If you have any questions, please contact [email protected]. We’re here to help.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
The issue has been resolved. Our team is investigating the root cause.
We are currently investigating this issue.
This incident has been resolved and Microsoft services are functioning as expected again. We apologize for the inconvenience, our team is investigating the root cause.
We are currently investigating this issue.
We are continuing to investigate the issue. Please avoid pressing "fix it for me" in Zite since the issue is platform level not per app.
An upstream provider is experiencing an outage, we are continuing to investigate and investigating solutions.
This incident has been resolved. We apologize for the disruption and are conducting a post-incident review to identify the root cause and prevent similar issues in the future.
We are currently investigating this issue.
We are continuing to see slowness, our team is continuing to investigate.
A fix has been implemented, and the slowness has stabilized. We are monitoring the results.
This incident has been resolved.
We are investigating an issue with an upstream provider.
We are seeing recovery across all services. Our team is continuing to monitor.
The outage has been marked as resolved by our upstream provider https://www.cloudflarestatus.com/ and we continue to see normal uptime.
We are currently investigating this issue.
The issue has been resolved, we are investigating to prevent this issue going forward.
This incident has been resolved.
We are currently investigating this issue.
This incident was resolved, we are no longer seeing an impact to form submissions. Our team is continuing to monitor and investigate the root cause.
We are investigating an issue causing some Zite databases to load slowly or not load at all. Data is still stored. This does not affect Fillout forms.
Zite databases are loading as expected. We are scaling our infrastructure and continuing to monitor.
An upstream provider is experience an outage, our team is investigating impact to Fillout
The issue is ongoing, we are tracking updates here https://www.cloudflarestatus.com/. Our team is continuing to investigate.
We are seeing recovering across most systems. Our team is continuing to monitor.
We are continuing to see issues for certain services. The upstream provider outage is ongoing. Our team is investigating.
The incident has been resolved by our infrastructure provider. We are no longer seeing issues with services but our team is continuing to monitor.
Our team is investigating. We are seeing an issue with our upstream cloud provider.
There is an ongoing issue with our upstream cloud provider. We are working with them to restore functionality as soon as possible.
The issue has been resolved by our upstream provider. We’re monitoring to confirm stability. Thank you for your patience and very sorry for the inconvenience.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
The main dashboard and forms were briefly offline (~90 seconds). Service has resumed, and we’re taking steps to address the root cause and prevent future impact.