This page will be updated in case of service disruption or other incidents preventing customers to use the application as usual.
All past disruptions since November 13, 2017 are also listed here.
October 06, 2020: Total service disruption
The App Engine service provided by Google experiences issues. It started at 2020-10-06 3:50PM CEST and ended at 2020-10-06 5:45PM CEST .
Due to App Engine outage, Awesome Table API service returned 500 error on every request. As a result, Awesome Table apps could not be loaded and users were not able to login on awesome-table.com.
Here's the Google incident report for more information:
https://status.cloud.google.com/incident/appengine/20007
This incident is now resolved.
October 11, 2018: Total service disruption
The Firebase Realtime Database service provided by Google experiences issues. It started at 2018-10-11 16h23 and ended at 2018-10-11 17h00 GMT-8.
As a result, the Awesome Table apps could not be loaded. The web application awesome-table.com did not function properly as well.
Here's the Firebase Database incident report for more information:
https://status.firebase.google.com/incident/Realtime Database/18058
This incident is now resolved.
August 08, 2018: Partial service disruption
The Firebase Hosting service provided by Google experiences issues. It started on 2018-08-08 and ended on 2018-08-09 09h30 GMT+2.
As a result, users could not login to the Awesome Table application. A "disabled sign-in" warning from Google would appear instead.
A second issue at the same time prevented Awesome Table apps to be embedded in external websites in some Regions.
This incident is now resolved.
July 17, 2018: Partial service outage
The Firebase Database service provided by Google experiences an issue where the database is not available. It started on 2018-07-17 12:20 GMT-8 and finished at 2018-07-17 13:09 GMT-8.
As a result, the Awesome Table apps may fail to load when opened, the Awesome-Table.com website will also not function as expected.
Here's the Firebase Database incident report for more information:
https://status.firebase.google.com/incident/Realtime Database/18046
This incident is now resolved.
February 28, 2018: Partial service outage
The Firebase Hosting service provided by Google experiences an issue where 503/504 errors are returned randomly when accessing domains. It started on 2018-02-28 04:24 GMT-8 and finished at 05:06 GMT-8.
As a result, the Awesome Table apps may fail to load when opened.
Here's the Firebase Database incident report for more information:
https://status.firebase.google.com/incident/Hosting/18003
This incident is now resolved.
February 1, 2018: Partial service outage
The Firebase Hosting service provided by Google experiences an issue where 503/504 errors are returned randomly when accessing domains. It started on 2018-2-01 1:45 PM GMT-8 and finished at 7:37 PM GTM-8. As a result, the Awesome Table apps may fail to load when opened.
Here's the Firebase Database incident report for more information:
https://status.firebase.google.com/incident/Hosting/18002
This incident is now resolved.
January 16, 2018: Increased Latency
The Firebase Database service provided by Google is facing an increased latency that started on 2018-1-16 2:40 PM GMT+1. As a result, Awesome Table service doesn't work as expected. More information will come soon.
Here's the Firebase Database incident report for more information:
https://status.firebase.google.com/incident/Realtime%20Database/18002
This incident is now resolved.
December 15, 2017: Partial service disruption
The Maps and Cards Awesome Table visualization have experienced issues with the use of column role's keywords, causing some of these visualizations to not be available from 2017-12-14 12:53 to 15 Dec 2017 08:23 GMT+2.
This incident is now resolved.
November 27, 2017: Service Disruption
The Firebase Database service provided by Google was not available from 2017-11-27 9:12 to 2017-11-27 10:30 GMT+2. As a result, Awesome Table was also not available.
Here's the Firebase Database incident report for more information:
https://status.firebase.google.com/incident/Realtime%20Database/17094
This incident is now resolved.