# Production broken for 24+ hours, no fix, no notification: time to say goodbye?

**URL:** <https://community.weweb.io/t/production-broken-for-24-hours-no-fix-no-notification-time-to-say-goodbye/18888>\
**Category:** Ask us anything\
**Created:** [June 23, 2025, 5:11am UTC](https://community.weweb.io/t/production-broken-for-24-hours-no-fix-no-notification-time-to-say-goodbye/18888 "2025-06-23T05:11:06Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![thipasbault](https://avatars.discourse-cdn.com/v4/letter/t/ee59a6/32.png) [@thipasbault](https://community.weweb.io/u/thipasbault)\
**Post date:** [June 23, 2025, 5:11am UTC](https://community.weweb.io/t/production-broken-for-24-hours-no-fix-no-notification-time-to-say-goodbye/18888/1 "2025-06-23T05:11:06Z")

</div>

Our production app has been down for more than 24h (probably saturday morning), and we’re not the only ones.  
Apparently Weweb team is aware of that but we’ve had ZERO notification [URGENT -- Weweb can't load collections? - #9 by BrancoDigital](https://community.weweb.io/t/urgent-weweb-cant-load-collections/18876/9).

Am I the only one that does not find it normal ?  
It’s the second time that Weweb fails for us, last time resulting in thousands of $ of waste in adspend.  
Spoler alert: they did not care at all, neither refunded us, nor gave a us any compensation on Weweb, just ended up ghosting us.

I love Weweb, maybe a little too much, and I’m starting to think no production app with a decent volume should rely on Weweb if your app can be down for days without them fixing it or even notifying you.

---

<div class="post-metadata">

**Author:** ![Dan\_OOT](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/dan_oot/32/14475_2.png) [@Dan\_OOT](https://community.weweb.io/u/Dan_OOT)\
**Post date:** [June 23, 2025, 6:40am UTC](https://community.weweb.io/t/production-broken-for-24-hours-no-fix-no-notification-time-to-say-goodbye/18888/2 "2025-06-23T06:40:20Z")

</div>

I’ve not been using the platform for long and I like it… but it’s concerning to have no notifications despite it being a known issue. I wasted hours of company time this morning trying to find out what was going on, assuming it was something I broke. While I’m relieved my work is solid, a simple notification/email/whatever would have saved me some very frustrating hours.

At least a notification would allow us to get ahead of customer complaints… even if a fix takes longer to happen.

---

<div class="post-metadata">

**Author:** ![alexanderl](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/alexanderl/32/9235_2.png) [@alexanderl](https://community.weweb.io/u/alexanderl)\
**Post date:** [June 23, 2025, 6:41am UTC](https://community.weweb.io/t/production-broken-for-24-hours-no-fix-no-notification-time-to-say-goodbye/18888/3 "2025-06-23T06:41:55Z")

</div>

I am out as well. Ridiculous. Just deploying on Friday and then closing their laptop for the weekend.

---

<div class="post-metadata">

**Author:** ![Dan\_OOT](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/dan_oot/32/14475_2.png) [@Dan\_OOT](https://community.weweb.io/u/Dan_OOT)\
**Post date:** [June 23, 2025, 6:49am UTC](https://community.weweb.io/t/production-broken-for-24-hours-no-fix-no-notification-time-to-say-goodbye/18888/4 "2025-06-23T06:49:30Z")

</div>

This is pretty much IT No-No #1, right?

---

<div class="post-metadata">

**Author:** ![RPAL](https://avatars.discourse-cdn.com/v4/letter/r/85f322/32.png) [@RPAL](https://community.weweb.io/u/RPAL)\
**Post date:** [June 23, 2025, 7:10am UTC](https://community.weweb.io/t/production-broken-for-24-hours-no-fix-no-notification-time-to-say-goodbye/18888/5 "2025-06-23T07:10:08Z")

</div>

Not particularly experienced with large scale production apps but I can absolutely feel the frustration of everyone here. There seems to be a pattern of instability and unreliability in what is otherwise a good product; surely the bad reputation is what leads people to competitors and not the need for more and more AI features.

---

<div class="post-metadata">

**Author:** ![Agustin\_Carozo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agustin_carozo/32/13231_2.png) [@Agustin\_Carozo](https://community.weweb.io/u/Agustin_Carozo)\
**Post date:** [June 24, 2025, 7:28am UTC](https://community.weweb.io/t/production-broken-for-24-hours-no-fix-no-notification-time-to-say-goodbye/18888/6 "2025-06-24T07:28:32Z")

</div>

Hello everyone, we’ve release an update on what happened:

> [@Update on the recent server failure issue](https://community.weweb.io/t/update-on-the-recent-server-failure-issue/18915):
>
> Between Saturday the 21st of June 2025, and Monday the 23rd of June 2025, we experienced a failure on our plugins server. As a result, data fetching for applications using the Airtable plugin, SQL plugin, and REST API plugin with CORS enabled in production was disrupted. This also impacted access to the editor for applications relying on these plugins. The issue has now been resolved, and the server is back to normal, functioning properly. The issue went undetected by our monitoring tools bec…

---

<div class="post-metadata">

**Author:** ![Kat](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/kat/32/5809_2.png) [@Kat](https://community.weweb.io/u/Kat)\
**Post date:** [June 24, 2025, 2:38pm UTC](https://community.weweb.io/t/production-broken-for-24-hours-no-fix-no-notification-time-to-say-goodbye/18888/7 "2025-06-24T14:38:39Z")

</div>

It is not resolved. We have has this problem for 3 weeks at least and are as well looking for other options because we can’t build here anymore.  
**You should stop your AI** , as it’s not important, what is important for us is RELIABILITY.

Don’t know about others but we came here for a bug free nocode platform.

---

<div class="post-metadata">

**Author:** ![Agustin\_Carozo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agustin_carozo/32/13231_2.png) [@Agustin\_Carozo](https://community.weweb.io/u/Agustin_Carozo)\
**Post date:** [June 24, 2025, 3:57pm UTC](https://community.weweb.io/t/production-broken-for-24-hours-no-fix-no-notification-time-to-say-goodbye/18888/8 "2025-06-24T15:57:34Z")

</div>

Hi @Kat I’m sorry you are experiencing these issues.

Have you reached out to our support through our chat interface?

---

<div class="post-metadata">

**Author:** ![Kat](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/kat/32/5809_2.png) [@Kat](https://community.weweb.io/u/Kat)\
**Post date:** [June 24, 2025, 5:46pm UTC](https://community.weweb.io/t/production-broken-for-24-hours-no-fix-no-notification-time-to-say-goodbye/18888/9 "2025-06-24T17:46:16Z")

</div>

from every possible channel. Today or yesterday we got one answer ‘going to look into it’ to a support request sent 21 DAYS ago.

In the meantime we had to:  
Make three product demos with the old version because no access to production.  
Had an investor meeting without having access to our product.  
Failed one live product demo, because something changed and it didn’t work.  
Served clients from FIGMA 😃 with personally doing what they want to do and updating database handmade for them, cause we can’t afford to lose them.  
Missed so many development milestones because of that mess.

Maybe Weweb is not anymore for people who want to build actual functioning MVPs?
