Is Grow.com Down Right Now? Check if there is a current outage ongoing.

The Grow app is currently experiencing intermittent service disruptions due to an ongoing incident with Cloudflare, our upstream CDN and DNS provider. This issue is affecting our ability to serve application traffic and respond to API requests. Our systems are fully operational, but because traffic is routed through Cloudflare, users may encounter timeouts, errors, or be unable to access the application during this period. We are actively monitoring the situation and will provide updates as Cloudflare releases more information or when we have a reliable workaround. For real-time updates, you may also follow Cloudflare's status page: https://www.cloudflarestatus.com We apologize for the inconvenience and appreciate your patience.

This incident has been resolved.

Grow has been experiencing intermittent performance issues. Performance has improved for some accounts but the situation continues to be monitored and improvements are continuing to be made. Please report any new performance issues to Grow Support.

This incident has been resolved.

A fix has been implemented, and we are monitoring the results.

We are continuing to investigate this issue.

We are currently investigating issues where the app is not loading or working slowly for some customers.

This was limited to one customer's rate limits. We are working on a permanent fix.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Many instances are receiving the error "You are calling a deprecated version of the Ads API.". We are looking into a solution as soon as possible.

The incident has been resolved.

A fix has been implemented and we are monitoring the results.

Users continue to experience slowness. Additional investigation into the cause of the issue is underway.

A fix has been implemented and we are monitoring the results.

Users may experience slow load times, blank pages, and errors when using Grow. This issue is intermittent and under investigation.

Grow is experiencing intermittent slowness. The issue is being investigated.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

An issue caused Grow to be down this morning. The system is back online but may run slow as things resolve.

This incident has been resolved.

A fix has been implemented and the jobs are processing. We will continue to monitor the results.

There is an issue with the process that refreshes the data for all connectors.

This incident has been resolved.

According to LinkedIn status, they are experiencing down time. https://www.linkedin-status.com/

This incident has been resolved.

Facebook and Instagram appear to be down. https://downdetector.com/status/facebook/

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are investigating an issue that appears to be causing some portion of data integrations to have failed or never started. Will continue to update as we learn more.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

A solution is currently being tested within our NPD environments.

The issue has been identified and a fix is being implemented.

Throughout this week, we've experienced performance degradation during the hour of 8AM PST. This has led to brief service outages lasting a few minutes, followed by continued performance issues for approximately 20-30 minutes. Our team promptly identified the underlying cause, but the initial solution partially addressed the issue. We understand the inconvenience this has caused and want to assure you that we are diligently working on a more effective resolution. Our goal is to implement a comprehensive fix by the end of today. We appreciate your patience and understanding as we strive to enhance your experience with our platform. Please do not hesitate to reach out to our customer support team for any assistance or further information.

This incident has been resolved.

A solution has been identified and will be implemented and tested this evening.

This week Grow has had brief outages of a few minutes that typically start around 8:05AM PST. We have identified the issue and are working to implement a solution.

This week Grow has had brief outages of a few minutes that typically start around 8:05AM PST. We have identified the issue and are working to implement a solution.

Issue with automated scaling caused a brief outage starting at 9:03AM, resolving after a few minutes.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

We are currently investigating this issue.

The incident has been resolved from the Facebook/Meta side of things.

A fix has been implemented and we are monitoring the results.

The issue has been identified. Facebook/Meta is having some issues with Login feature. https://metastatus.com/?ref=dfc&fbclid=IwAR0jjYndWhe4lQZBmglTvqfgI53CJi7q_eyJtMkAAlhlOdrS7OzlibHQW78#developerplatform

This incident has been resolved.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

Our Twitter connector is down. We have been notified that our application has been suspended, most likely due to the new tiers launch. We have submitted a ticket to get more information and appeal the decision. This has not affected our Twitter Ads connector. More details to follow.

On March 29th, 2023 we were informed by Twitter that new API Access tiers were launched. The plan option the Grow connector utilizes is scheduled to encounter heavy restriction beginning on April 29th, 2023. As of right now, no restrictions have been applied and the Twitter connections within Grow remain operational. If Twitter does not revert this decision, we anticipate that Twitter connections in Grow will encounter error messages beginning April 29th. In reviewing the new API Access tiers provided by Twitter, the Grow team has determined that we will not be able to continue supporting a native Twitter connector should these changes go into effect April 29th. Given these updates, our recommendation is to explore alternative ways to get this data into Grow in order to minimize any disruption. Please note the only communication we have received related to this is specific to the Twitter API and does not make any mention of the Twitter Ads API. At this time the Grow team will do everything possible to maintain the Twitter Ads API as it currently stands. We will continue to monitor the situation and will post relevant updates here as we have them. While this decision is out of our control, we do apologize for any inconvenience this may cause. Please reach out to our support team if you have any questions.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

We have experienced a temporary outage of our integration authentication service. A fix has been implemented and we are monitoring the results.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We recently found an update affecting metric tile positioning issues. Existing metrics with a “copy” source may have been reset on their tile positions. We are looking into what dashboards may have been affected and have paused grow-app usage to prevent further dashboards from being potentially affected.

We are currently investigating this issue.

This incident has been resolved. Our DevOps team inadvertently deployed code towards the wrong targets, which caused the servers associated with our Kubernetes clusters to become temporarily unavailable.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

We are continuing to monitor for any further issues.

Grow is back online and AWS has confirmed that they have resolved the issue on their end. We will continue to monitor the situation.

The issue has been identified as an outage on the AWS servers that Grow uses.

We are continuing to investigate this issue.

We are currently investigating this issue.

The errors can be resolved by re-authenticating. We will be sending out more detailed information to affected users. If you have any further questions or concerns, please do not hesitate to reach out to our support team at support@grow.com.

We are continuing to monitor for any further issues.

We are currently experiencing an issue with Shopify connections returning the following error message. "An error has occurred with the Shopify servers. Please wait a few minutes and try again." Our team has identified that the error is related to an update to our permissions that has is requiring a re-authentication to Shopify for our users. If your connection has been made before March 16th, 2023 we recommend re-authenticating. We apologize for any inconvenience this may cause. If you have any further questions or concerns, please do not hesitate to reach out to our support team at support@grow.com.

This incident has been resolved.

Grow's connection to LinkedIn Ads has been disrupted and users are unable to reconnect. We are currently investigating the issue and will provide updates as soon as we have any.

The incident has been resolved. We have deployed a fix that will pull the data in based on the format that Shopify has redesigned. For those impacted, further details will be sent out. Thank you for your patience.

Supplier location info within the Orders Line Items warehouse table is currently returning no information. We have identified the issue and are working on a fix.

Backwards compatibility appears to be working. If you are receiving any error messages that contain "Potentially a bad profile id or you do not have permissions" please navigate to the connection and reconnect.

We are continuing to monitor for any further issues.

UPDATE(12/15/2022): The new business page has been approved by Facebook. We are currently testing with a subset of accounts to ensure backwards compatibility. If you are receiving any error messages that contain "Potentially a bad profile id or you do not have permissions" please navigate to the connection and reconnect. --------------- ORIGINAL(11/15/2022): We were informed by Facebook that our connectors may experience restrictions beginning Nov 6th. As of right now, no restrictions have been applied and we are continuing to monitor the situation. The Grow team is actively working towards migrating our connectors to a new Business page without any restrictions to avoid disruption as proactively as possible. Once the new business page has been approved by Facebook, a reconnection in Grow may be required upon our deployment.

The limit has been reset and we have taken appropriate measures to ensure that the limit will not be met going forward.

All Twitter Warehoused Tables are returning an error. We have identified the the Twitter Warehoused Tables in Grow are returning an error message related to rate limits for the version of the Twitter API we use to connect. The limit will reset on March 16th, 2023 and the warehoused tables should have the historical data up to the point the error message was encountered. Should you need more immediate access to Twitter data before March 16th, our Direct Query method utilizes a different version of the API and is able to return data. In the meantime we are actively working to explore alternative ways to populate the data in the warehoused tables to mitigate the risk of this occurring in the future. We apologize for the disruption. If you have any questions, please reach out to support@grow.com

We had identified an incident with some connections with our authentication service that caused them to require a reconnection. This issue has now been resolved. We apologize for any inconvenience this may have caused. If you have an invalid connection please reconnect. If you have any further questions, please reach out to support@grow.com

Deals and Contacts warehouse tables were not pulling in some columns or some of their values. This issue has now been resolved. We apologize for any inconvenience this may have caused. If you have any further questions, please reach out to support@grow.com

We had a brief outage following a misconfiguration in our deployment pipeline. The problem was quickly identified and fixed.

This incident has been resolved.

The issues affecting Instagram have been resolved. The Facebook Ads issue is still impacting a small subset of customers and we are looking into warehousing the Facebook Ads connection as a possible solution for those still impacted. We appreciate your patience and apologize for the inconvenience this may have caused.

We have identified the issue with Instagram and have implemented a fix. For Facebook Ads, we are continuing to work through the issues.

Facebook's Graph API is having some disruptions. They have been ongoing since June 9th 11:58AM MDT. https://status.fb.com/graph-api We will update as we find out more information from Facebook.

Grow experienced roughly a 5 minute outage following an infrastructure deployment that was incorrectly targeted at the wrong environment clusters.

This incident has been resolved.

We are continuing to investigate this issue.

The Grow App services are currently down. We are investigating the issue and will keep you posted as soon as we have an update.

This incident has been resolved.

Grow is experiencing minor performance issues on the whitelabel server with intermittent but rare spikes that significantly decrease performance and may result in 504 responses. We've identified the problem and will be working on a resolution as soon as possible.

This incident has been resolved.

Grow is experiencing minor performance issues with intermittent but rare spikes that significantly decrease performance and may result in 504 responses. We've identified the problem and will be working on a resolution as soon as possible.

This incident has been resolved.

We are continuing to work on a fix for this issue.

We’ve identified the issue and are taking steps to address this as quickly as possible.

Grow's connection to Facebook has been disrupted. We are currently investigating the issue and will provide updates as soon as we have any.

Users have asked whether Grow is affected by the recent log4j incident. Grow does not use the log4j library and it is not susceptible to this vulnerability. If you have any questions or concerns, please contact our team at support@grow.com.

Amazon has resolved their issues.

Amazon Web Services are currently experiencing degraded performance affecting the Grow App. Please refer to their status page for more information: https://status.aws.amazon.com/

Our White label branded portals upgrades have been completed. Thank you for your understanding as we continually work towards a more stable and performant service.

Our White label branded portals are currently being upgraded to align with Grow's primary application services (app.gogrow.com). This upgrade is expected to be completed early December. Until the upgrade is completed, white label branded portals may experience intermittent connectivity or performance issues. We apologize for this inconvenience. Thank you for your patience as we work towards improving this experience for you and your customers.

The Grow App services went down from 1:31–1:34 PM MST today, 3 December, 2021. This outage was due to human error. We apologize for the inconvenience. We have asked the engineer responsible to take a mental health day off and get a full night’s rest. 😀

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Some users have reported issues accessing their Saved Reports through the Salesforce Direct Query connection. We are currently investigating the issue.

This issue has now been resolved. We apologize for any inconvenience this may have caused. If you have any further questions, please reach out to support@grow.com

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results. Thank you for your understanding as we work to improve the experience and reliability of Custom Branded Domains. As we monitor the fix, please reach out to support@grow.com if you continue to have any issues.

Customers may have trouble loading or connecting to Grow through Custom Branded Domains at this time. Grow is still accessible via app.gogrow.com. Our team is investigating and we'll follow up with more information as soon as we have it. We apologize for any disruption caused.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

Some users are seeing error messages when trying to connect to certain database data sources. We are currently investigating the issue.

This issue has now been resolved. We apologize for any inconvenience this may have caused. If you have any further questions, please reach out to support@grow.com

We have identified the issues and a fix has been implemented and we are monitoring the results. Thank you for your understanding as we work to improve the experience and reliability of our branded domain services. As we monitor the fix, please reach out to support@grow.com if you continue to have any issues.

Custom Branded Domains continue to display a 502 Gateway Error. We are actively investigating the issue. We apologize for any disruption caused.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

Customers may have trouble loading or connecting to Grow through Custom Branded Domains at this time. Grow is still accessible via app.gogrow.com. Our team is investigating and we'll follow up with more information as soon as we have it. We apologize for any disruption caused.

This incident has been resolved.

Customers may have trouble loading or connecting to Grow through Custom Branded Domains at this time. Grow is still accessible via app.gogrow.com. Our team is investigating and we'll follow up with more information as soon as we have it. We apologize for any disruption caused.

This incident has been resolved.

Facebook has implemented a fix and we are monitoring the results. For more information, please visit Facebook's status page: https://status.fb.com/

Customers may have trouble loading or connecting to Facebook, Facebook Ads, or Instagram Business data at this time. This is a Facebook issue and we're monitoring their status updates. Facebook status page: https://status.fb.com/

Customers may have trouble loading or connecting to Facebook, Facebook Ads, or Instagram Business data at this time. This is a Facebook issue and we're monitoring their status updates.

Grow uses Amazon Web Services and they were reporting a major outage from Friday evening through Saturday morning August 6-7, 2021. Unfortunately, Grow was down during this period. See more at https://status.aws.amazon.com/

Grow's primary NGINX web servers encountered upstream dependency issue that prevented horizontal scaling. A hotfix was deployed and the outage was resolved in 16 minutes. All Grow application services are expected to be restored.

We are continuing to investigate this issue.

Customers may have trouble loading or connecting to Grow at this time. Our team is investigating and we'll follow up with more information as soon as we have it. We apologize for any disruption caused.