# Abandoned Load Balancer on 884-9095 upgrade

**URL:** <https://forum.datomic.com/t/abandoned-load-balancer-on-884-9095-upgrade/1994>\
**Category:** Datomic Cloud\
**Created:** [November 2, 2021, 4:31pm UTC](https://forum.datomic.com/t/abandoned-load-balancer-on-884-9095-upgrade/1994 "2021-11-02T16:31:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![caleb](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/caleb/32/87_2.png) [@caleb](https://forum.datomic.com/u/caleb)\
**Post date:** [November 2, 2021, 4:31pm UTC](https://forum.datomic.com/t/abandoned-load-balancer-on-884-9095-upgrade/1994/1 "2021-11-02T16:31:35Z")

</div>

When I upgraded my production topology compute group to 884-9095, it encountered the following error while trying to clean up the old network load balancer:

> Load balancer ‘xxx’ cannot be deleted because it is currently associated with another service (Service: AmazonElasticLoadBalancing; Status Code: 400; Error Code: ResourceInUse; Request ID: xxx; Proxy: null)

The upgrade finished without any other problems and my query groups did not have this problem (they also did not have API Gateway lambda proxies), but now I have a single network load balancer left over (with the datomic:system tag). The load balancer is the one referenced in the above error message.

Is it safe for me to manually delete the network load balancer?

Thanks,  
Caleb

UPDATE: I think the delete was actually blocked by an old Vpc Endpoint Service

---

<div class="post-metadata">

**Author:** ![jaret](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/jaret/32/45_2.png) [@jaret](https://forum.datomic.com/u/jaret)\
**Post date:** [November 2, 2021, 5:06pm UTC](https://forum.datomic.com/t/abandoned-load-balancer-on-884-9095-upgrade/1994/2 "2021-11-02T17:06:22Z")

</div>

Yes you can delete the NLB. As of [884-9095](https://docs.datomic.com/cloud/changes.html#884-9095), each compute group now uses an ALB instead of an NLB.