# Fibery currently down?

**URL:** <https://community.fibery.io/t/fibery-currently-down/5413>\
**Category:** Bugs & Issues\
**Created:** [November 16, 2023, 12:11pm UTC](https://community.fibery.io/t/fibery-currently-down/5413 "2023-11-16T12:11:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel\_Chiniquy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/daniel_chiniquy/32/6955_2.png) [@Daniel\_Chiniquy](https://community.fibery.io/u/Daniel_Chiniquy)\
**Post date:** [November 16, 2023, 12:11pm UTC](https://community.fibery.io/t/fibery-currently-down/5413/1 "2023-11-16T12:11:07Z")

</div>

We are getting errors and extreme slowness / no reply from the fibery server currently. Anyone else having issues?  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/758fdcf5bf6246a2c0bcd95584871f49ff604683.png)

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [November 16, 2023, 12:12pm UTC](https://community.fibery.io/t/fibery-currently-down/5413/2 "2023-11-16T12:12:40Z")

</div>

Yep, sorry. We’re on it.

---

<div class="post-metadata">

**Author:** ![bear](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bear/32/12872_2.png) [@bear](https://community.fibery.io/u/bear)\
**Post date:** [November 16, 2023, 3:05pm UTC](https://community.fibery.io/t/fibery-currently-down/5413/3 "2023-11-16T15:05:31Z")

</div>

Good luck! 💪💪💪💪💪

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [November 16, 2023, 4:51pm UTC](https://community.fibery.io/t/fibery-currently-down/5413/4 "2023-11-16T16:51:57Z")

</div>

Resolved. It was mostly unstable, not down.

During a specific time period, there were issues with core pods restarting intermittently. This was caused by sub-optimal new ACL logic in the Views service, resulting in high CPU usage and Redis errors. The logic triggered a large number of requests in a short period of time, causing increased memory consumption and cache eviction. This led to more requests to Redis, some of which failed, and increased CPU and thread usage.