Grow.com Outage History
12 incidents recorded over the last 365 days, 1 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 Grow.com Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 1, 2026 | Scheduled MaintenanceWe will be undergoing scheduled maintenance during this time. This maintenance may cause brief intermittent service outages with the Grow platform. Please be aware that your "Needs Attention" page may temporarily show… | 3h 0m | Scheduled |
| Sep 28, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Sep 25, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Sep 16, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Aug 28, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Aug 27, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Aug 26, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Aug 12, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Aug 1, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jun 6, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Apr 27, 2026 | Facebook Ads Connector OutageThis incident has been resolved. | 3h 54m | Resolved |
| Mar 15, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
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 Grow.com 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 Grow.com 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 Grow.com 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 Grow.com outage in this window ran 3h 54m, against a mean recovery of 2h 25m. If you depend on Grow.com 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.