Incidents and maintenance reported on status page for LWS https://lws.betteruptime.com/ en https://lws.betteruptime.com/incident/308222 Fri, 05 Jan 2024 20:56:00 -0000 https://lws.betteruptime.com/incident/308222#edb7ec132345dd88c5f24c0cc1999de7a9b4c76b0e174027f31c58db1931ced3 Incident Our backend provider has solved the issue, we have reverted to the correct APIs, thank you for your patience. https://lws.betteruptime.com/incident/308222 Fri, 05 Jan 2024 03:59:00 -0000 https://lws.betteruptime.com/incident/308222#46876912e4710589c71e11b83cce2ac7707e0a0bbe02eb9919770940f5b9729b Incident We have contacted our backend provider to inform them of the issue. We will update this page once the problem is resolved or we get a response. https://lws.betteruptime.com/incident/308222 Thu, 04 Jan 2024 03:57:00 -0000 https://lws.betteruptime.com/incident/308222#da181df1f10e9f6748c8c6ae9527bfd9263eb546a806d64398f4e4adac31861d Incident ## What's happening: Our backend provider is experiencing issues when we request meeting stats filtered for our preset, global Group ID. ## How are we resolving the issue: To mitigate this issue we are sending the entire account's usage, not just a specific Group ID. This will not affect usage stats at this time. ## Technical Explanation: LWS isn't multitenant, but our backend provider supports multitenancy, so to stay within best practices, we implemented one Group ID called "lws_default" and asked the API for usage data that pertains only to that Group ID, currently that API isn't available, so we are using the account wide API, that doesn't affect us outside of not being proper implementation. We will update the status once the API comes back online. Thank you.