# Deployment health issue: Snapshots out of date (latest success was 23 hours ago) **URL:** \ **Category:** Elasticsearch\ **Created:** [December 24, 2018, 10:01am UTC](https://discuss.elastic.co/t/deployment-health-issue-snapshots-out-of-date-latest-success-was-23-hours-ago/161993 "2018-12-24T10:01:05Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![princeOfMacedon](https://avatars.discourse-cdn.com/v4/letter/p/f04885/32.png) [@princeOfMacedon](https://discuss.elastic.co/u/princeOfMacedon)\ **Post date:** [December 24, 2018, 10:01am UTC](https://discuss.elastic.co/t/deployment-health-issue-snapshots-out-of-date-latest-success-was-23-hours-ago/161993/1 "2018-12-24T10:01:05Z")
Hi all, I'm using filebeat to push log to elastic cloud. After using elastic-curator to add snapshots and backup some old indices to S3, I've encounter this error on elastic cloud console: Deployment health issue: Snapshots out of date (latest success was 23 hours ago) Can someone provide me some insight about this. Thanks in advanced! ---
**Author:** ![zanbel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zanbel/32/20678_2.png) [@zanbel](https://discuss.elastic.co/u/zanbel)\ **Post date:** [December 24, 2018, 10:41am UTC](https://discuss.elastic.co/t/deployment-health-issue-snapshots-out-of-date-latest-success-was-23-hours-ago/161993/2 "2018-12-24T10:41:09Z")
Hey @princeOfMacedon, This forum is actually for Elastic Cloud Enterprise (ECE) which is a different product. Can you please follow these [instructions](https://www.elastic.co/cloud/as-a-service/support) and open a ticket. You can also do it directly from the user console, under the [help section](https://cloud.elastic.co/help) ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [December 24, 2018, 3:56pm UTC](https://discuss.elastic.co/t/deployment-health-issue-snapshots-out-of-date-latest-success-was-23-hours-ago/161993/3 "2018-12-24T15:56:40Z")
Actually, the response belongs here. That warning is only triggered for the built-in snapshots for ECE. If you set up custom snapshots using Curator, they will _not_ affect this message at all. ---
**Author:** ![princeOfMacedon](https://avatars.discourse-cdn.com/v4/letter/p/f04885/32.png) [@princeOfMacedon](https://discuss.elastic.co/u/princeOfMacedon)\ **Post date:** [December 26, 2018, 4:57am UTC](https://discuss.elastic.co/t/deployment-health-issue-snapshots-out-of-date-latest-success-was-23-hours-ago/161993/4 "2018-12-26T04:57:54Z")
I'm not sure which elastic product I use, is it ECE. I'm using a cluster with a dashboard in [cloud.elastic.co](http://cloud.elastic.co) My question is what cause this error warning. And can I safely ignore this as my system works without any known problems. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [December 26, 2018, 6:00am UTC](https://discuss.elastic.co/t/deployment-health-issue-snapshots-out-of-date-latest-success-was-23-hours-ago/161993/5 "2018-12-26T06:00:37Z")
Please see [https://www.elastic.co/cloud/as-a-service/support](https://www.elastic.co/cloud/as-a-service/support) on how to raise a support ticket for Elastic Cloud 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 9, 2019, 6:00am UTC](https://discuss.elastic.co/t/deployment-health-issue-snapshots-out-of-date-latest-success-was-23-hours-ago/161993/6 "2019-01-09T06:00:42Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.