GoFormz Outage History

Started Sep 23, 2026, 08:00 PM UTC· resolved Oct 12, 2026, 10:06 PM UTC

1. investigating Sep 23, 2026, 08:00 PM UTC

   We're currently experiencing an SSL certificate issue affecting www.goformz.com due to a recent domain migration. Visitors may see a browser warning when visiting the site while we complete domain verification and reissue the certificate. Our other domains and services are not impacted and continue to operate normally

2. resolved Oct 12, 2026, 10:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 16, 2026, 03:56 PM UTC· resolved Apr 16, 2026, 05:38 PM UTC

1. investigating Apr 16, 2026, 03:56 PM UTC

   We are currently experiencing a major outage impacting all Web GoFormz services.

2. monitoring Apr 16, 2026, 04:23 PM UTC

   A fix has been implemented and all services are back to normal operation. We will follow up with a post mortem ASAP.

3. resolved Apr 16, 2026, 05:38 PM UTC

   This incident has been resolved. Please read on for a full post mortem of the incident. GoFormz Service Disruption on April 16, 2026 On April 16, 2026, GoFormz experienced a service disruption that made our application slow or unreachable for many users over a roughly 35-minute window. We know reliability is critical to your business, and we apologize for the disruption. Root Cause On April 15, 2026, GoFormz rolled out a maintenance process designed to clean up expired transient data in our database and keep the system running efficiently. After approximately 24 hours, this process began conflicting with normal application activity under real-world usage, causing database deadlocks. These deadlocks blocked access to our core database, leading to significant application latency and user-facing timeouts. The issue was mitigated by disabling the cleanup service and increasing database capacity. Impact to Customers: Application latency and user-facing timeouts. - Start of impact: 8:23 AM PDT - Mitigation began: 8:55 AM PDT - Service restored: 8:59 AM PDT During this window, you may have experienced very slow response times, login attempts that timed out in your browser, or been unable to access the application altogether. Why We Didn't Catch It Sooner GoFormz runs automated tests around the clock that simulate user logins to confirm the application is working. These tests only validated success, not performance. What We're Doing About It 1. We will be redesigning this database maintenance process so it cannot interfere with normal application activity, regardless of load. 2. Better monitoring. We're adjusting speed thresholds to our automated tests and adding a new layer of alerts so we're alerted the moment the application becomes too slow under such circumstances. This will address the gap in login performance testing. Again, we apologize for the disruption. If you have any questions, please reach out to our support team.

Read the full incident report →

Started Dec 16, 2025, 05:04 PM UTC· resolved Dec 17, 2025, 03:48 PM UTC

1. investigating Dec 16, 2025, 05:04 PM UTC

   We are currently investigating an issue with filtered datasource fields in our web app and mobile apps for some clients. Our engineering team is actively diagnosing the root cause and working to restore normal functionality. We will continue to monitor the situation and provide updates shortly.

2. identified Dec 16, 2025, 05:13 PM UTC

   The GoFormz engineering team has identified the issue which is isolated to mobile, filtered Datasource fields only. The team is currently working on a fix, and will release updates shortly.

3. resolved Dec 17, 2025, 03:48 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 29, 2025, 04:08 PM UTC· resolved Oct 30, 2025, 03:25 PM UTC

1. investigating Oct 29, 2025, 04:08 PM UTC

   We are currently experiencing a major outage impacting all Web GoFormz services. This disruption is due to a widespread Microsoft Azure outage, which is affecting our infrastructure and related services. The GoFormz team is actively investigating the issue and monitoring Azure’s recovery efforts. We will provide updates here as soon as more information becomes available. Thank you for your patience and understanding while we work to restore full functionality.

2. identified Oct 29, 2025, 05:25 PM UTC

   After investigating the impact of the Microsoft Azure outage, we have moved Automated Workflows, Mobile Apps, Email Delivery, and API services to Operational. These services should be functioning as expected. Web App, Login, and Public Forms services are still experiencing a major outage. Microsoft Azure is continuing to investigate and implement a fix to address this outage. For further details, please see the latest update from Microsoft Azure: https://azure.status.microsoft/en-us/status We will continue to monitor the situation and provide updates as more information becomes available.

3. monitoring Oct 29, 2025, 09:00 PM UTC

   Microsoft Azure has implemented a fix, and all GoFormz services are now operating as expected. We are continuing to monitor and will share the Azure post-mortem when available.

4. resolved Oct 30, 2025, 03:25 PM UTC

   This incident has been resolved. A post-mortem provided by Microsoft Azure will be posted shortly.

5. postmortem Oct 30, 2025, 03:25 PM UTC

   [https://azure.status.microsoft/en-us/status/history/](https://azure.status.microsoft/en-us/status/history/) The following information was shared by Microsoft Azure following this incident. > _This is our Preliminary PIR to share what we know so far. After our internal retrospective is completed \(generally within 14 days\) we will publish a Final PIR with additional details._ > > **What happened?** > > Between 15:45 UTC on 29 October and 00:05 UTC on 30 October 2025, customers and Microsoft services leveraging Azure Front Door \(AFD\) may have experienced latencies, timeouts, and errors. > > Affected Azure services include, but are not limited to: App Service, Azure Active Directory B2C, Azure Communication Services, Azure Databricks, Azure Healthcare APIs, Azure Maps, Azure Portal, Azure SQL Database, Azure Virtual Desktop, Container Registry, Media Services, Microsoft Copilot for Security, Microsoft Defender External Attack Surface Management, Microsoft Entra ID \(Mobility Management Policy Service, Identity & Access Management, and User Management UX\), Microsoft Purview, Microsoft Sentinel \(Threat Intelligence\), and Video Indexer. > > Customer configuration changes to AFD remain temporarily blocked. We will notify customers once this block has been lifted. While error rates and latency are back to pre-incident levels, a small number of customers may still be seeing issues and we are still working to mitigate this long tail. Updates will be provided directly via Azure Service Health. > > **What went wrong and why?** > > An inadvertent tenant configuration change within Azure Front Door \(AFD\) triggered a widespread service disruption affecting both Microsoft services and customer applications dependent on AFD for global content delivery. The change introduced an invalid or inconsistent configuration state that caused a significant number of AFD nodes to fail to load properly, leading to increased latencies, timeouts, and connection errors for downstream services. > > As unhealthy nodes dropped out of the global pool, traffic distribution across healthy nodes became imbalanced, amplifying the impact and causing intermittent availability even for regions that were partially healthy. We immediately blocked all further configuration changes to prevent additional propagation of the faulty state and began deploying a ‘last known good’ configuration across the global fleet. Recovery required reloading configurations across a large number of nodes and rebalancing traffic gradually to avoid overload conditions as nodes returned to service. This deliberate, phased recovery was necessary to stabilize the system while restoring scale and ensuring no recurrence of the issue. > > The trigger was traced to a faulty tenant configuration deployment process. Our protection mechanisms, to validate and block any erroneous deployments, failed due to a software defect which allowed the deployment to bypass safety validations. Safeguards have since been reviewed and additional validation and rollback controls have been immediately implemented to prevent similar issues in the future. > > **How did we respond?** > > 15:45 UTC on 29 October 2025 – Customer impact began. > > 16:04 UTC on 29 October 2025 – Investigation commenced following monitoring alerts being triggered. > > 16:15 UTC on 29 October 2025 – We began the investigation and started to examine configuration changes within AFD. > > 16:18 UTC on 29 October 2025 – Initial communication posted to our public status page. > > 16:20 UTC on 29 October 2025 – Targeted communications to impacted customers sent to Azure Service Health. > > 17:26 UTC on 29 October 2025 – Azure portal failed away from Azure Front Door. > > 17:30 UTC on 29 October 2025 – We blocked all new customer configuration changes to prevent further impact. > > 17:40 UTC on 29 October 2025 – We initiated the deployment of our ‘last known good’ configuration. > > 18:30 UTC on 29 October 2025 – We started to push the fixed configuration globally. > > 18:45 UTC on 29 October 2025 – Manual recovery of nodes commenced while gradual routing of traffic to healthy nodes began after the fixed configuration was pushed globally. > > 23:15 UTC on 29 October 2025 - PowerApps mitigation of dependency, and customers confirm mitigation. > > 00:05 UTC on 30 October 2025 – AFD impact confirmed mitigated for customers. > > **What happens next?** > > Our team will be completing an internal retrospective to understand the incident in more detail and will share findings within 14 days. Once we complete our internal retrospective, generally within 14 days, we will publish a final Post Incident Review \(PIR\) to all impacted customers.

Read the full incident report →

Started Sep 16, 2025, 03:16 PM UTC· resolved Sep 17, 2025, 12:03 AM UTC

1. identified Sep 16, 2025, 03:16 PM UTC

   We are currently experiencing issues with Email Delivery via Workflow and Template events due to an interruption with our email provider, SendGrid. This is impacting all accounts. Our team is actively working with SendGrid to restore services as quickly as possible. We will provide updates as soon as more information becomes available.

2. identified Sep 16, 2025, 08:29 PM UTC

   We are continuing to work with SendGrid to resolve the issue affecting Email Delivery via Workflow and Template events. The problem is still impacting all accounts. We will provide the next update as soon as more information is available.

3. resolved Sep 17, 2025, 12:03 AM UTC

   The issue affecting Email Delivery via Workflow and Template events caused by a SendGrid interruption has been fully resolved. Email delivery is now functioning normally across all accounts. We will continue to monitor, but no further impact is expected.

4. postmortem Sep 17, 2025, 05:11 PM UTC

   ### Postmortem: Email Delivery Interruption **Incident Duration:** * **Start:** Tuesday, September 16, 2025 at approximately 7:50 AM PT * **End:** Tuesday, September 16, 2025 at approximately 5:00 PM PT **Impact:** During this incident, **Email Delivery via Workflow, Template events, and Account Management \(reset password/invite user emails\)** were unavailable for all GoFormz accounts. **Root Cause:** Our email provider temporarily suspended outbound traffic from GoFormz due to suspicious activity. * **Important:** At no point was customer data exposed or put at risk. The suspicious activity was isolated to those specific accounts. **Resolution:** GoFormz worked closely with our provider to validate the issue, secure our systems, and restore normal service. **How this impacts you:** Most emails triggered to be sent during this time period _**were ultimately delivered after resolution.**_ However, some were not delivered. For those impacted emails, please follow the below remediation instructions: * **Template Events:** Re-trigger manually \(e.g., by opening/completing the form again\). * **Workflow Jobs:** Select the “...” actions button to the right of the job and click **“Rerun.”** * Customers can rerun these jobs one by one. * If you have a significant number of jobs to rerun, please reach out to our support team at [**[email protected]**](mailto:[email protected]) and we can help you bulk rerun batches. * **Password Reset Emails:** Resend password reset requests. Customers can resend in bulk from the **Users & Groups** page. **Preventive Measures:** We have strengthened safeguards with our email provider and are improving monitoring to reduce the likelihood of similar interruptions in the future.

Read the full incident report →

Started Aug 25, 2025, 03:50 PM UTC· resolved Aug 26, 2025, 03:52 PM UTC

1. identified Aug 25, 2025, 03:50 PM UTC

   We’ve identified a bug affecting checkbox fields on forms in the mobile app. Following last week’s app update (August 21 for Android, August 22 for iOS), checkbox and checkbox group values may show the incorrect value after form completion. This affects all users who are using the mobile app version 4.0.1391 and have completed forms with checkboxes since their respective app releases last week. We are actively working on a fix and will provide an update as soon as a resolution is available.

2. monitoring Aug 25, 2025, 07:51 PM UTC

   A fix has been implemented and released to the mobile app stores (Android and iOS). Please update to the latest mobile app version: 4.0.1395. Users must update to this mobile app version to resolve the issue on their device. We are continuing to monitor, and we will share a post-mortem shortly.

3. resolved Aug 26, 2025, 03:52 PM UTC

   This incident has been resolved. We will share a post-mortem shortly.

4. postmortem Aug 26, 2025, 03:52 PM UTC

   **Postmortem: Mobile checkbox display issue \(August 21–25, 2025\)** **Resolved:** August 25, 2025 at 12:22 PM PT **Impact window:** August 21–25, 2025 **Affected platforms:** Android, iOS and Windows mobile apps \(version 4.0.1391\) **Issue summary:** Between August 21 and August 25, a bug in GoFormz mobile app version 4.0.1391 caused checkbox and checkbox group values to sometimes display incorrectly. The issue was limited to mobile forms using these field types and did not affect all forms and completions. **Root cause:** A recent mobile release introduced a logic error that affected how checkbox states were saved during certain form interactions. This led to a mismatch between user input and the final stored values. **Resolution:** The issue was resolved with mobile app version 4.0.1395, released to all app stores on August 25. Users must update to this version to prevent further occurrences. **Next steps for customers:** We recommend reviewing forms submitted between August 21 and August 25 using the mobile app version 4.0.1391, especially if they include checkbox fields. Not all forms in this timeframe are confirmed to be impacted, but reviewing them will help ensure data accuracy. **Preventive actions:** We are implementing additional automated testing for field-specific behavior in mobile forms and improving release QA processes for core field logic. We appreciate the customers who flagged this issue quickly and thank you for your patience while we worked toward a resolution.

Read the full incident report →

Started Aug 19, 2025, 06:34 PM UTC· resolved Aug 19, 2025, 10:04 PM UTC

1. investigating Aug 19, 2025, 06:34 PM UTC

   We are currently investigating an issue preventing users from logging into the GoFormz mobile app. Some users may experience issues accessing the app at this time. Our engineering team is actively diagnosing the root cause and working to restore normal functionality. We will continue to monitor the situation and provide updates shortly.

2. monitoring Aug 19, 2025, 06:50 PM UTC

   This issue has now been fixed. If you are continuing to experience issues, please follow the resolution steps below. 1. Tap Login as usual. The app may attempt to load and then return you to the main screen. 2. Tap Login again. You should then be successfully signed in. If you continue to be unable to login, please contact your account representative or [email protected]. Our team is continuing to monitor the status and investigate the root cause of this behavior.

3. resolved Aug 19, 2025, 10:04 PM UTC

   This incident has been resolved. A postmortem has been posted with further details about this incident.

4. postmortem Aug 19, 2025, 10:05 PM UTC

   **Postmortem - Mobile login Interruptions** **What Happened** On August 19, from 10:18 am to 10:46 am PT, some users experienced issues logging into the GoFormz mobile app. This was related to recent updates made in preparation for upcoming infrastructure enhancements aimed at improving system performance. **Resolution** Impacted users saw full resolution by 11:36am through a rollback of the sync service. On some devices, cached settings may have delayed full recovery. Pressing the login button again clears the cache and restores access. We are refining our release processes to ensure continued reliability during future platform improvements.

Read the full incident report →

Started Aug 04, 2025, 02:24 AM UTC· resolved Aug 04, 2025, 04:57 PM UTC

1. investigating Aug 04, 2025, 02:24 AM UTC

   We are currently investigating an intermittent error that shows when accessing parts of the GoFormz Web App. Impact includes access to some pages of the Web App and Workflow/email delivery automations.

2. monitoring Aug 04, 2025, 02:58 AM UTC

   A fix has been implemented, and all services have been restored to operational status. We are continuing to monitor as performance remains stable.

3. resolved Aug 04, 2025, 04:57 PM UTC

   This incident has been resolved. A post-mortem will be shared shortly.

4. postmortem Aug 04, 2025, 05:18 PM UTC

   ### **Post-Incident Summary** On Sunday, August 3rd, GoFormz experienced a disruption impacting the Web Application, including access to certain pages and execution of automations \(Workflow and Template Events\). We understand how critical these functions are, and we sincerely apologize for the inconvenience this caused. ### **Incident Details** **What happened** Part of the GoFormz infrastructure responsible for the Web Application became unresponsive, causing intermittent failures when users attempted to access some pages and the related services mentioned above. **Resolution** Once the issue was identified, our engineering team worked closely with Microsoft Azure to isolate and remove the impacted infrastructure. We are continuing to closely monitor the impacted services. ‌ If you have any questions or are still experiencing issues, please reach out to our support team at [[email protected]](mailto:[email protected]) or your account representative.

Read the full incident report →

Started Jul 23, 2025, 03:38 PM UTC· resolved Jul 23, 2025, 10:44 PM UTC

1. monitoring Jul 23, 2025, 03:38 PM UTC

   Starting at approximately 8:00am Pacific time the GoFormz Web App platform began experience interrupted performance. This was resolved at approximately 8:30am Pacific time. We are continuing to monitor performance.

2. monitoring Jul 23, 2025, 10:44 PM UTC

   This issue is now resolved, and a post-mortem has been posted.

3. resolved Jul 23, 2025, 10:44 PM UTC

   This incident has been resolved.

4. postmortem Jul 23, 2025, 10:45 PM UTC

   **What happened:** Starting at approximately 8:00 a.m. Pacific Time, the GoFormz Web App platform began experiencing intermittent performance issues. This was resolved at approximately 8:30am Pacific time. **Root cause:** Following today's regular production release, it was identified that a configuration of the management system supporting the web application was incorrect. The GoFormz Engineering team quickly resolved this issue, fixing the interruption. Please contact your account representative or [[email protected]](mailto:[email protected]) if you have any additional questions.

Read the full incident report →

Started Mar 03, 2025, 03:59 PM UTC· resolved Mar 03, 2025, 10:47 PM UTC

1. investigating Mar 03, 2025, 03:59 PM UTC

   Some accounts may be experiencing intermittent issues when attempting to log in to the GoFormz platform. We are investigating the cause of these errors and will share an update shortly.

2. monitoring Mar 03, 2025, 07:09 PM UTC

   The root cause of this issue has been identified, and a fix has been implemented. All services are operating as expected. We are continuing to monitor performance.

3. resolved Mar 03, 2025, 10:47 PM UTC

   This issue is now resolved, as we have continued to see stable performance throughout the day. If you have any further questions, please contact your account manager or email [email protected].

4. postmortem Mar 03, 2025, 10:47 PM UTC

   At approximately 7:20 am PT on Monday, March 3rd, it was identified that some GoFormz users were experiencing errors when logging into the platform. The GoFormz Engineering team quickly investigated and found that Microsoft Azure released an update that impacted our CDN layer. At approximately 11:10 am PT on Monday, March 3rd, the GoFormz Engineering team implemented a fix and restored all users’ ability to access the GoFormz platform as expected. This issue is now resolved, as we have continued to see stable performance throughout the day. If you have any further questions, please contact your account manager or email [[email protected]](mailto:[email protected]).

Read the full incident report →

Started Dec 26, 2024, 09:12 PM UTC· resolved Dec 27, 2024, 05:44 PM UTC

1. investigating Dec 26, 2024, 09:12 PM UTC

   We are experiencing interrupted performance throughout several areas of the platform, due to a power outage impacting several Azure Datacenters. We will continue to monitor performance and availability. More Info available at Azure's status page - https://azure.status.microsoft/en-us/status

2. identified Dec 26, 2024, 09:20 PM UTC

   From Azure's Engineers: Starting at 18:44 UTC on 26 Dec 2024, there was a power incident in a portion of South Central US AZ03 which impacted one of the three physical AZ, affecting multiple services. We are currently investigating and attempting to restore the service More Info available at Azure's status page - https://azure.status.microsoft/en-us/status

3. monitoring Dec 27, 2024, 05:06 PM UTC

   As of 9:22 PM PST, all functionality on the GoFormz platform has been restored. Our engineers are continuing to investigate any potential impacts on our system. An ongoing incident at the Azure Datacenter persists, and we will continue to monitor our system's performance closely.

4. resolved Dec 27, 2024, 05:44 PM UTC

   This incident has been resolved.

Read the full incident report →