Is there an GoFormz outage?
GoFormz status: Systems Active
Last checked: 7 minutes ago
Get notified about any outages, downtime or incidents for GoFormz and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 7 minutes ago
Get notified about any outages, downtime or incidents for GoFormz and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for GoFormz.
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 (v2) | Active |
| Automated Workflows | Active |
| Email Delivery | Active |
| Mobile Sync API | Active |
| Web App | Active |
| Web App - Support Chat Bubble | Active |
| Mobile Apps | Active |
| Andoird App | Active |
| iOS App | Active |
| Windows App | Active |
View the latest incidents for GoFormz and check for official updates:
Description: At approximately 10:24 AM today, GoFormz began to experience issues triggering events on a mobile device. We have rolled back the update causing this issue and are continuing to monitor affected accounts. At this time, events are firing as expected, however, all forms completed between 10:24 AM and 12:20 PM PDT did not trigger events or workflows as expected. To re-fire these events, please reopen and complete the form. This will only need to be done for forms expected to trigger an event and completed during this timeframe from a mobile device.
Status: Resolved
Impact: None | Started At: June 4, 2019, 7:50 p.m.
Description: After service recovery, the Microsoft Azure team is providing more detail regarding the service disruption that occurred on May 2, 2019. Here is that detail directly from Microsoft: > Network Connectivity - DNS Resolution > > **Summary of impact:** Between 19:43 and 22:35 UTC on 02 May 2019, customers may have experienced intermittent connectivity issues with Azure and other Microsoft services \(including M365, Dynamics, DevOps, etc\). Most services were recovered by 21:30 UTC with the remaining recovered by 22:35 UTC. > > **Preliminary root cause:** Engineers identified the underlying root cause as a nameserver delegation change affecting DNS resolution and resulting in downstream impact to Compute, Storage, App Service, AAD, and SQL Database services. During the migration of a legacy DNS system to Azure DNS, some domains for Microsoft services were incorrectly updated. No customer DNS records were impacted during this incident, and the availability of Azure DNS remained at 100% throughout the incident. The problem impacted only records for Microsoft services. > > **Mitigation:** To mitigate, engineers corrected the nameserver delegation issue. Applications and services that accessed the incorrectly configured domains may have cached the incorrect information, leading to a longer restoration time until their cached information expired. > > **Next steps:** Engineers will continue to investigate to establish the full root cause and prevent future occurrences. A detailed RCA will be provided within approximately 72 hours.
Status: Postmortem
Impact: Major | Started At: May 2, 2019, 7:57 p.m.
Description: After service recovery, the Microsoft Azure team is providing more detail regarding the service disruption that occurred on May 2, 2019. Here is that detail directly from Microsoft: > Network Connectivity - DNS Resolution > > **Summary of impact:** Between 19:43 and 22:35 UTC on 02 May 2019, customers may have experienced intermittent connectivity issues with Azure and other Microsoft services \(including M365, Dynamics, DevOps, etc\). Most services were recovered by 21:30 UTC with the remaining recovered by 22:35 UTC. > > **Preliminary root cause:** Engineers identified the underlying root cause as a nameserver delegation change affecting DNS resolution and resulting in downstream impact to Compute, Storage, App Service, AAD, and SQL Database services. During the migration of a legacy DNS system to Azure DNS, some domains for Microsoft services were incorrectly updated. No customer DNS records were impacted during this incident, and the availability of Azure DNS remained at 100% throughout the incident. The problem impacted only records for Microsoft services. > > **Mitigation:** To mitigate, engineers corrected the nameserver delegation issue. Applications and services that accessed the incorrectly configured domains may have cached the incorrect information, leading to a longer restoration time until their cached information expired. > > **Next steps:** Engineers will continue to investigate to establish the full root cause and prevent future occurrences. A detailed RCA will be provided within approximately 72 hours.
Status: Postmortem
Impact: Major | Started At: May 2, 2019, 7:57 p.m.
Description: From approximately 8:38am PDT to 8:50am PDT on Monday, April 29th, GoFormz Workflow and API services experienced degraded performance. GoFormz engineering performed standard troubleshooting steps and returned the services to normal operations. GoFormz will continue to monitor these services.
Status: Resolved
Impact: Minor | Started At: April 29, 2019, 5:54 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: March 18, 2019, 9:30 p.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.
