12:15 PM Eastern – As of 9:30 AM, Portal Group 6 content has been synchronized to reflect a restore point of 2/12 – 11:30 PM ET
5AM Eastern – We have now restored service to Classic CMS PG6 as well. We will closely monitor to ensure that all systems are responding appropriately. A comprehensive root cause analysis will be perform to identify improvement opportunities.
We once again want to apologize for the impact to your business and we will strive to greatly improve the level of service being delivered to our customers
3:30AM Eastern – We have restored service to the Classic CMS on portal groups 5 ,7 and 8.
This issue is believed to be due to a database cluster stability issue. We have transferred 3 of the 4 impacted systems, PG5, PG7, and PG8, to our backup database configurations as of 11:00pm ET 2/12/14.
The Classic CMS 6 is still being actively worked to restore service and validate full functionality. We will communicate when service has been fully restored to this system
We apologize for the impact to your business and we strive to never have downtime to the content we host on your behalf.
We will determine the needed improvements immediately to rectify any further issues.
1:39 AM Eastern – This issue continues to impact the content hosted on Classic CMS 5, 6, 7, and 8. We continue to working aggressively to resolve the issue. We apologize for the inconvenience, Updates to follow..
12:39 AM Eastern – We continue to experience issues during a routine maintenance that is impacting content hosted on Classic CMS 5, 6, 7, and 8. We are working aggressively to resolve the issue and work with our provider to resolve the issue. Updates to follow..
11:29 PM Eastern – We are experiencing issues during a routine maintenance that is impacting content hosted on Classic CMS 5, 6, 7, and 8. We are working to resolve the issue and our operations team is actively working to resolve the issue.
11:14 PM Eastern — Since 10:59 PM Eastern, customer content hosted on Classic CMS 5 is not loading. HubSpot Engineering is engaged and is working to resolve the issue.