All Systems Operational
CloudHealth Platform ? Operational
CloudHealth API ? Operational
CloudHealth REST API ? Operational
Support Site Operational
CloudHealth Partner Platform Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Oct 21, 2019
Resolved - AWS has generated current CURs for all customers and CloudHealth has collected and process the currently available CURs on our normal schedule. We believe all correctly configured accounts should be showing the current information available. If you have any issues or question, please contact us at support@cloudhealthtech.com
Oct 21, 11:03 EDT
Update - AWS is in the process of generating updated Cost and Usage Reports (CURs) and we are seeing that many of our customers have started to receive them. AWS expects to be caught up by 5PM PST today, so many of our customers will be seeing updated information today or tomorrow depending on exactly when they receive the CURs in their S3 buckets. It may be possible that a late generation of the CUR could miss the processing window for our platform and updated reports will not be generated until Sunday. We will be monitoring this over the weekend.

Please contact Support (support@cloudhealthtech.com) with any further questions.
Oct 18, 11:23 EDT
Update - We have learned that AWS expects to restart generating CURs at approximately 9:30pm ET. Customers should expect to start receiving updated CURs after that point, but we do not know how long this process will take for them. Given this rolling execution, we expect that we won’t receive many CURs for processing until tomorrow and thus Platform data and reports may not be up to date until Saturday, October 19, 2019. We will continue to provide updates here as we receive new information.

Please contact support (support@cloudhealthtech.com) with any questions.
Oct 17, 13:50 EDT
Monitoring - We have identified multiple accounts where AWS has not generated a recent Cost and Usage report within the configured S3 billing bucket.

Cost and Usage manifest data shows many accounts have not had a recent billing update in the past 20hrs.

This is expected to result in delayed AWS reporting data within the CloudHealth platform.

We will provide a further status update once we determine that AWS has updated Cost and Usage reports.
Oct 17, 00:59 EDT
Oct 20, 2019

No incidents reported.

Oct 19, 2019

No incidents reported.

Oct 16, 2019

No incidents reported.

Oct 15, 2019
Resolved - The CloudHealth platform experienced degraded AWS asset collection from approximately 12:00PM EDT 10/15/2019 to 8:40AM EDT 10/16/2019.

Collection during this period was intermittent; as such, short-lived assets created and terminated during this period may have incomplete metadata.

Please email support@cloudhealthtech.com with any questions.
Oct 15, 12:00 EDT
Oct 14, 2019

No incidents reported.

Oct 13, 2019

No incidents reported.

Oct 12, 2019
Resolved - This incident has been resolved.

Please contact support@cloudhealthtech.com with any questions.
Oct 12, 08:57 EDT
Monitoring - The fix has been deployed and we expect the all AWS accounts to update to the correct account status tomorrow.

Please contact support@cloudhealthtech.com with any questions.
Oct 11, 13:43 EDT
Identified - The CloudHealth platform is experiencing an issue where AWS accounts may unexpectedly report a 'No Current Billing' 'Account Type' state even though the Account is configured correctly with valid credentials.

You may also see a warning banner advising -

"We've detected that you do not have an AWS Cost and Usage report (CUR) configured for these accounts: . CloudHealth is no longer reporting on costs for these accounts. To resume cost reporting for these accounts, complete the configuration or contact your CloudHealth Administrator."

This is a known issue that is actively being worked on by our engineering team and it does not impact the collection of AWS data.

One side effect of this issue is that RI Recommendation tools may not operate as intended while accounts are in this state as they may not be evaluating on a full set of accounts.

If you experience this issue where your accounts are configured correctly with a 'Heathy' status but you observe a 'No Current Billing' 'Account Type' state please reach out to support@cloudhealthtech.com to have a manual workaround applied.

We will provide further updates once a full fix is in place.
Oct 10, 23:36 EDT
Oct 10, 2019
Resolved - This incident is now considered resolved.

All assets have now been collected however we may still be missing some short-lived:

S3 Buckets, Kinesis Streams, Sagemaker Notebook Instances, EMR Clusters, EC2 Snapshots, RDS Snapshots, EC2 Nat Gateway.

That were run during the outage window.

Please contact support@cloudhealthtech.com with any questions.
Oct 10, 03:34 EDT
Investigating - Due to an incident around 12am EDT any short-lived assets types from the following categories: S3 Buckets, Kinesis Streams, Sagemaker Notebook Instances, EMR Clusters, EC2 Snapshots, RDS Snapshots, EC2 Nat Gateways may not be collected.

The issue with collection is now resolved and we're processing again, this may result in a delay in collection.
Oct 10, 03:05 EDT
Oct 9, 2019

No incidents reported.

Oct 8, 2019
Resolved - The fix for this issue is now in place and the September Partner billing re-run is now complete.

Please contact support@cloudhealthtech.com for any follow-up questions.
Oct 8, 18:17 EDT
Monitoring - The fix has been deployed and we are rerunning September billing for all affected customers. We expect the rerun to be visible in reports and statements tomorrow.

Please contact support@cloudhealthtech.com with any questions.
Oct 7, 17:02 EDT
Identified - Our engineering team has identified the root cause. We are in the process designing a fix and expect to review and test the fix by tomorrow. We will then deploy the fix and normal nightly processing will update all reports and statements for customers. Please contact support@cloudhealthtech.com if you have any questions.
Oct 6, 19:40 EDT
Update - Our Engineering team is still working on the issue with data transfer costs for September and October not reflecting the proper customer pricing tier. We will post updates as they are available. Currently, billing information for customers using CloudHealth Partner Generated Billing is not correct. Please contact support@cloudhealthtech.com if you have any questions.
Oct 6, 18:41 EDT
Investigating - We have identified an issue where partner generated billing is passing through tiered pricing cost for some AWS services. Our engineering teams are currently investigating this matter.

Please contact support@cloudhealthtech.com with any questions.
Oct 6, 15:05 EDT
Oct 7, 2019
Resolved - This incident has been resolved.

Please contact support@cloudhealthtech.com with any questions.
Oct 7, 13:33 EDT
Identified - We have identified the issue and corrected it. We are now re-processing jobs for CloudHealth Statements and Reports. Updated information should be available over the next few hours for those customers impacted by this issue.

If you have any questions, contact support@cloudhealthtech.com.
Oct 7, 11:14 EDT
Investigating - We have identified an issue where CloudHealth Statements and Reports show $0.00 spend in 2019-09 for some CSP customers. Our engineering teams are currently investigating this matter.

Please reach out to support@cloudhealthtech.com with any questions.
Oct 7, 05:25 EDT