Workflow

LumApps Workflow (web and mobile)

Time Status Message
3 years, 4 months ago Up LumApps is actively responding to the reported remote code execution vulnerability in the Apache Log4j 2 Java library dubbed Log4Shell (or LogJam). We investigated and took actions for LumApps services that could have been impacted. Here are the results of our investigations: - No critical services in LumWork were impacted (mainly Python services) - Unexposed services (MongoDB database, communication services, ...) are not impacted
3 years, 5 months ago Up LumWork is up again. No data has been lost during the interruption. Sorry for the inconvenience
3 years, 5 months ago Down We are currently having issues with our databases, causing LumWork to be down for most users. We are working on it and will let you know as soon as it is back up
4 years, 9 months ago Up LumWork is back up, thank you for your patience.
4 years, 9 months ago Warning We are currently performing a scheduled maintenance, we will be back in 20-30 minutes. Sorry for the inconvenience.
4 years, 10 months ago Up LumWork should be up again: after Google's incident resolution, we noticed that some services didn't restart automatically. We restarted them and everything should be back. We apologise for the service interruption.
4 years, 10 months ago Down As of today 11pm French Time, Google services are not fully restored, so LumWork is still down. We will keep you updated as soon as we have updates about it. Sorry for the inconvenience.
4 years, 10 months ago Down We are still investigation the issue, it seems like it comes from a Google Cloud Platform issue as a few services are currently down: https://status.cloud.google.com/ (and in particular, for us: https://status.cloud.google.com/incident/cloud-memorystore/20002)
4 years, 10 months ago Down There is currently an issue to access LumWork. We are investigating it and will let you know as soon as we have more details about it. Sorry for the inconvenience.
5 years ago Up Google has solve its internal issue, everything is back to normal now.
5 years ago Warning There is currently an issue with the Space Reporting feature. It is caused by a global issue in Google Cloud Platform, hosting our infrastructure: https://status.cloud.google.com/incident/zall/20005
5 years, 5 months ago Up The issue has been solved by Google, and updating the sharings in LumWork should be working again. Following is the status update from Google: https://www.google.com/appsstatus#v=issue&sid=10&iid=b5dc1f8a365f641ebeea2c33847e8e6a
5 years, 5 months ago Warning There is currently an issue in updating LumWork Spaces' sharings. This is due to an issue in Google Directory API. We have contacted Google, and will let you know as soon as we have more information about it. Sorry for the inconvenience.
5 years, 10 months ago Up LumWork is back again. We will give you Google's update when they update their status dashboard. Sorry for the inconvencience that is not due to an error on our side.
5 years, 10 months ago Down Update: Google reported new issues with Google cloud networking, which are causing LumWork to be down: https://status.cloud.google.com/incident/cloud-networking/19016
5 years, 10 months ago Down Update: LumWork is still down, the Google cloud networking issue is now resolved but there seem to be an issue with Google app engine, see the message at the top of the page: https://status.cloud.google.com/ we will let you know once we know more about it
5 years, 10 months ago Down We are currently investigating an issue with LumWork, you might get a 502 message when trying to access LumWork. It is due to an issue with Google infrastructure, see https://status.cloud.google.com/incident/cloud-networking/19015 We will let you know once we have an update.
5 years, 11 months ago Up LumWork add-on should now be available again following Google approval. Sorry for the inconvenience.
5 years, 11 months ago Warning There is currently an issue with LumWork add-on: new users get a message indicating that Google sign in has been temporarily disabled. We are working on it, waiting for Google to validate our update that fixes this. Thank you for your patience.
6 years, 1 month ago Up Here's the full debrief from our provider, Google: Start Time: 5:45 PM UTC Recovery Time: 6:40 PM UTC Root Cause: This was caused due to a loss of service in the intermediary layer of the service within AppEngine that would also encompass Cloud Endpoints. This issue would result in malfunctioning API calls on the public LumApps API used by the web application and mobile applications. We are sorry about the inconvenience caused by this event.
6 years, 1 month ago Up The issue was resolved by our provider (Google) around 6:40 PM UTC. We'll post a full debrief later on when we have more information to share.
6 years, 1 month ago Down We confirm that we have an issue with our provider (Google). We are working closely with them to identify the root cause of this problem. We will update you in 30 minutes.
6 years, 1 month ago Up The latest published LumDrive extension (v0.8.50) solves the issue encountered by users who updated to Chrome 73. Thank you for your patience
6 years, 1 month ago Up The issue with the G Suite applications launcher, resulting in 502 errors, should now have been solved by Google. Thank you for your patience.
6 years, 1 month ago Warning We are encountering an issue with the LumDrive extension for users who updated their Chrome browser to version 73 and upper and can't see their LumDrive spaces in Google Drive. While we are trying to fix this ASAP, you can do the following workaround: go to "chrome://flags", then search and disable the "Enable network service" feature. Thank you for your patience.
6 years, 1 month ago Warning There is currently a known issue with the G Suite applications launcher, that might result in a 502 error. The issue is on Google's side, impacting all G Suite marketplace applications and we are working with them to fix it ASAP. In the meantime, users can use https://work.lumapps.com/ to connect to LumWork.
6 years, 6 months ago Up The Document Search feature is now completely back. Thank you for your patience
6 years, 6 months ago Up LumWork is now back, the Document Search feature might take a few more minutes to be completely back.
6 years, 6 months ago Warning We are currently doing a schedule maintenance that will last at most 1 hour. Sorry for the inconvenience.
6 years, 7 months ago Up The LumWork Add-on and Extension are now up again for everyone. Thank you for your patience.
6 years, 7 months ago Warning We are currently experimenting an issue with the "Open in Office" feature with the LumWork extension. We are working on this and will update this status as soon as it is restored. Sorry for the inconvenience.
6 years, 7 months ago Warning There is currently an issue with the LumWork add-on, which is not available on the Chrome Store. We are working on this and will update this status as soon as it is restored. Sorry for the inconvenience.
6 years, 7 months ago Up Service was restored at 9.30am CEST. We apologize for the inconvenience.
6 years, 7 months ago Down LumWork was unreachable this morning (European time) due to an issue with the internal backend server.
6 years, 11 months ago Up LumWork is now reachable again. We had an issue with the load balancing of the database cluster. We apologize for the inconvenience.
6 years, 11 months ago Down LumWork is unreachable. We're investigating and update as soon as we have more information.
7 years, 3 months ago Up "Error servers" were due to some App Engine instances that have not been deleted when deploying a new version. We have deleted manually these instances and are going to open a ticket to Google.
7 years, 3 months ago Warning Some customers are experimenting a "server error" sometimes when loading LumWork. Seems that a refresh of the page allows loading LumWork. We are investigating and will provide feedback as soon as possible
7 years, 4 months ago Warning In some cases, LumWork add-on is not retrieving the full list of records. We are analyzing the reason why it happens
7 years, 4 months ago Up LumWork was unreacheable for some customers due to changes in Google infrastructure. New quota has been allocated to avoid such situation in the future, and access has been restored at 9:00 CEST for impacted customers.
7 years, 4 months ago Warning LumWork has been unreachable for some customers on 2017-12-15 starting at 8:00 CEST
7 years, 5 months ago Up This issue with our provider is now fixed, we are sorry for the inconvenience.
7 years, 5 months ago Down There's an ongoing issue with our provider cache system. We'll update as soon as we have more information.
8 years ago Up Latencies experimented during the last 50 minutes are now solved, and we will lead actions to avoid such behaviour in the future
8 years ago Warning Some users may encounter "Server error" and slowness when accessing to LumWork. We are investigating the root cause and how to come back to normal as soon as possible.
8 years, 4 months ago Up Google groups synchronization is now complete and every access has been restored for every users
8 years, 4 months ago Warning We are experimenting some issues in Google groups synchronization and we have started a new synchronization
8 years, 5 months ago Up Version 0.8.36 is now displaying LumWork logo in Google Drive when using LumWork Chrome extension
8 years, 5 months ago Warning Due to an unexpected change in Google Drive UI, LumWork logo is not displayed in Google Drive when using LumWork Chrome extension.
8 years, 6 months ago Up The service has been fully restored. It started failing around 12:30 PM GMT and was fully working approximately 1 hour later. Our first investigations pointed connectivity issues between the application and the database that were non trivial to fix due to the complex nature of our infrastructure.
8 years, 6 months ago Down We are currently experiencing issues with the service. We will let you know as soon as we have more information.
8 years, 7 months ago Up Users having uppercase characters in their email have now a full access to LumWork spaces.
8 years, 7 months ago Warning Due to the 20/10/2016 unforecasted Google Group APIs update, users that have a uppercase letter in their email address may experiment difficulties to access to some spaces. Situation will be back to normal for all users in the next 3 hours.
8 years, 7 months ago Up The Group Synchronization issue we faced in LumWork is due to an unexpected Google Groups APIs change. We have updated our application to match this new behavior of the Google Groups APIs and groups are under synchronization.
8 years, 7 months ago Warning Some Google Groups members are not displayed in LumWork. We are investigating to identify the root cause as soon as possible. This can cause a "Permission denied" when trying to access a space or a document
8 years, 7 months ago Warning You might have experimented "Server error" and slowness when using LumWork in the previous days. The root cause has been identified and fixed in our backend and won't happen again. We are continuously working on improving performances of our platform to provide you the best user experience.
8 years, 7 months ago Up Access to LumWork is now restored to every user on the platform and we are investigating what happened.
8 years, 7 months ago Warning Some users may encounter difficulties when accessing to LumWork. We are investigating the root cause and how to come back to normal as soon as possible
8 years, 8 months ago Up
8 years, 9 months ago Warning Version 0.8.17 of the Chrome extension had an issue during deployment that has been solved by 0.8.18. Manual update can be forced as described in our FAQ https://help.lumapps.com/lumwork/use/user-installation/chrome-extension-user-installation/chrome-extension-faq
8 years, 9 months ago Up Google fixed the infrastructure issue and there shouldn't be random server errors anymore.
8 years, 9 months ago Warning We are currently experiencing some random server errors. Most of the time, a page refresh solve the issue but it might result in an application slowdown. We are currently working with the Google support team to resolve this issue as soon as possible.
8 years, 10 months ago Up Latencies experimented during the last 50 minutes are now solved, and we will lead actions to avoid such behaviour in the future
8 years, 10 months ago Warning We are currently experimenting latencies and we are investigating the reason why you may experiment some difficulties while using LumWork
8 years, 10 months ago Up Users and groups management issue in space sharing is now back to normal and we will continue monitoring it during the coming days.
8 years, 10 months ago Warning We are actually experimenting an issue in the user and group management, so you may experiment difficulties when adding or deleting users or groups in your LumWork spaces. We are investigating this issue, and will let you know as soon as we have more information.
8 years, 11 months ago Up We have resolved the previous issue with our DNS provider. We've seen the first errors yesterday around 5:10 pm (Paris Time) and was fixed at 5:40 pm (Paris Time). The issue was linked to our DNS provider service and was not linked to our products. The service is back to normal, we apologize for the inconvenience.
8 years, 11 months ago Up Sites hosted on work.lumapps.com are now available. We are still monitoring the situation and we will give a full debrief soon.
8 years, 11 months ago Down We are currently facing an issue with our DNS provider. All sites hosted on work.lumapps.com are currently unavailable. We will let you know as soon as we have more information.
8 years, 11 months ago Up
8 years, 11 months ago Warning Google deployed a new minor version of Drive that breaks the LumWork extension v0.8.8. The version 0.8.9 of the extension fix this issue. It has already been pushed to the Chrome Webstore. No action is required on your side, Chrome will automatically update it soon.
9 years ago Up The LumWork Chrome extension version 0.8.5 fixes the issue. This new version will be deployed automatically by Chrome in a couple of hours.
9 years ago Warning We are currently investigating an issue with the LumWork Chrome extension.
9 years ago Up Everything is back to normal. For more information on the underlying issue, please look at https://status.cloud.google.com/incident/appengine/16003
9 years ago Warning There is an on-going issue with the Google login. Users might see a 500 error during connection. They can try to refresh the page to see the Google login page. For more information, see https://status.cloud.google.com/incident/appengine/16003
9 years, 2 months ago Up Error messages are now displayed correctly to users.
9 years, 2 months ago Warning Due to an infrastructure limitation, some user may encounter the error message "A server error occurred" instead of the actual message explaining why there is an error. Most of the time, this happens when the user token is about to expire and a simple page reloads should solve the issue. We are actively working on a solution.

Status Legend

  • Down

    The service is currently down

  • Warning

    The service is experiencing intermittent problems

  • Up

    The service is up