# Context Deadline Exceeded - Shared Cluster not usable anymore

**URL:** <https://discuss.dgraph.io/t/context-deadline-exceeded-shared-cluster-not-usable-anymore/17862>\
**Category:** Dgraph Cloud\
**Tags:** kind:bug\
**Created:** [October 12, 2022, 3:43pm UTC](https://discuss.dgraph.io/t/context-deadline-exceeded-shared-cluster-not-usable-anymore/17862 "2022-10-12T15:43:18Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Poolshark](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/poolshark/32/10074_2.png) [@Poolshark](https://discuss.dgraph.io/u/Poolshark)\
**Post date:** [October 12, 2022, 3:43pm UTC](https://discuss.dgraph.io/t/context-deadline-exceeded-shared-cluster-not-usable-anymore/17862/1 "2022-10-12T15:43:18Z")

</div>

_Another day, another try of getting some response… (this forum and the server)_

For almost the entire day our Shared Cluster (AWS US-west) returns

```auto
Context Deadline Exceeded

```

This happened in the past but not as frequently and not for an entire day! So we basically can’t use the service we are paying for…

Any fixes? Any suggestions?

---

<div class="post-metadata">

**Author:** ![MichelDiz](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/micheldiz/32/11873_2.png) [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)\
**Post date:** [October 12, 2022, 7:01pm UTC](https://discuss.dgraph.io/t/context-deadline-exceeded-shared-cluster-not-usable-anymore/17862/2 "2022-10-12T19:01:39Z")

</div>

Update: We have someone working on it.

---

<div class="post-metadata">

**Author:** ![Poolshark](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/poolshark/32/10074_2.png) [@Poolshark](https://discuss.dgraph.io/u/Poolshark)\
**Post date:** [October 12, 2022, 7:42pm UTC](https://discuss.dgraph.io/t/context-deadline-exceeded-shared-cluster-not-usable-anymore/17862/3 "2022-10-12T19:42:23Z")

</div>

@MichelDiz thanks for the update! Can you tell how long the expected downtime will roughly be? Do you guys already know where the issue is origination from? Hopefully not my Shared Instance 😜

---

<div class="post-metadata">

**Author:** ![Poolshark](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/poolshark/32/10074_2.png) [@Poolshark](https://discuss.dgraph.io/u/Poolshark)\
**Post date:** [October 13, 2022, 7:46am UTC](https://discuss.dgraph.io/t/context-deadline-exceeded-shared-cluster-not-usable-anymore/17862/4 "2022-10-13T07:46:59Z")

</div>

**Update:** It seems to be working again!

Is there any information on how this has happened? Must we expect more downtimes in the future?

Thanks!

---

<div class="post-metadata">

**Author:** ![MichelDiz](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/micheldiz/32/11873_2.png) [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)\
**Post date:** [October 13, 2022, 5:00pm UTC](https://discuss.dgraph.io/t/context-deadline-exceeded-shared-cluster-not-usable-anymore/17862/5 "2022-10-13T17:00:55Z")

</div>

See

> **[Connectivity issues for Shared and Free backends in AWS us-east-1](https://status.dgraph.io/incidents/h4klb9jmfk8f)**
>
> Dgraph Cloud's Status Page - Connectivity issues for Shared and Free backends in AWS us-east-1.

> [@Poolshark](#):
>
> Is there any information on how this has happened?

I think maybe we can’t, because it’s information about the internal structure.

> [@Poolshark](#):
>
> Must we expect more downtimes in the future?

Analyzing the internal conversations, it seems to me to be a sporadic problem.

---

<div class="post-metadata">

**Author:** ![Poolshark](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/poolshark/32/10074_2.png) [@Poolshark](https://discuss.dgraph.io/u/Poolshark)\
**Post date:** [October 13, 2022, 6:04pm UTC](https://discuss.dgraph.io/t/context-deadline-exceeded-shared-cluster-not-usable-anymore/17862/6 "2022-10-13T18:04:46Z")

</div>

@MichelDiz

> [@MichelDiz](#):
>
> I think maybe we can’t, because it’s information about the internal structure.

Fair enough.

> [@MichelDiz](#):
>
> Analyzing the internal conversations, it seems to me to be a sporadic problem.

It did happen in the past and it was getting more frequently within recent weeks. Searching the forum there are more people being affected. Let’s hope it is fixed! 🙌

Thanks for the effort!