GrowthZone Outage History
10 incidents recorded over the last 365 days, 7 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded GrowthZone Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 14, 2026 | Access to third-party integrationsThis incident has been resolved. Thank you for your patience. | 7h 13m | Resolved |
| Sep 24, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Aug 21, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Aug 3, 2026 | Some GrowthZone customers are experiencing system latencyThis incident has been resolved. | 9h 29m | Resolved |
| Jul 16, 2026 | Degraded System Performance: Login/Authentication IssuesLogin and authentication services have been restored. Our vendor was able to restore service by rerouting traffic around the impacted AWS infrastructure. Please note the underlying AWS issue may still be ongoing, but it… | 1h 2m | Resolved |
| Jun 25, 2026 | System MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| May 11, 2026 | GZ CMS Sites Slow or UnavailableThis incident has been resolved. | 1h 26m | Resolved |
| Apr 6, 2026 | System latency - Some customers are experiencing slowness in the GrowthZone softwareThis incident has been resolved. | 59 min | Resolved |
| Jan 27, 2026 | Some customers are not able to log into their GrowthZone databaseThis incident has been resolved. | 2h 44m | Resolved |
| Jan 26, 2026 | GrowthZone/Quickbooks connection issueThis incident has been resolved. | 1h 4m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next GrowthZone incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This GrowthZone Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before GrowthZone acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single GrowthZone outage in this window ran 9h 29m, against a mean recovery of 2h 54m. If you depend on GrowthZone in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.