Update 3 - Dec 20
The gloebit company reports they have fixed the outage. Please test to see if it is working for you. Later today we will revert region Seattle to Gloebits.


The Gloebit WEB site and services went offline around 4AM grid time. This is a metaverse outage and no estimate on repair completion. The Gloebit company is aware of the situation and they are working on it. Details are here https://FaceBook.com/Gloebit

If you see error message "remote server not found (404)" this is the Gloebit money module reporting it cannot connect to Gloebit servers.

UPDATE1 from Gloebit Dec 14 7PM Pacific

(From Gloebit FB page) We are still experiencing an outage today. Amazon Elastic Beanstalk was claiming that our service was up and running fine but we couldn't retrieve any logs or connect. Re-deploys continued to provide the same experience. Our identical sandbox environment remained running, so this did not appear to be an issue with our system. While experimenting to resolve this issue, we took down and could not restore our production environment on Amazon EB. We are working with their support to bring the service back up. We do not have an ETA on restoration. This is not the first time we've had an outage due to Amazon EB, so we will explore other platform options in the future.

UPDATE2 from Gloebit Dec 17

 

(From Gloebit FB page) Tonight we received some information from the AWS support team which should help us get the service restored. We are still working on it and apologize for such a lengthy outage.

 



Monday, December 14, 2020

« Back