Really need a Glowforge status dashboard



I am currently unable to use my Glowforge as it is marked as “offline” in the app. It was working perfectly earlier today and my internet connection is fine (I’m using it to write this post).

@dan, could you please prioritize the creation of a Glowforge service health/status dashboard? It’s really frustrating to try and troubleshoot problems of this nature without some indication of whether or not there is a problem with the Glowforge services.

Some examples of the type of dashboard that I am looking for can be found here:

I consider this to be a fundamental feature for any service that is 100% dependent on cloud services. I would be surprised if anyone in the Glowforge user community disagrees with the need for this.


This is critical. Thank you for bringing it up.


A must have as well as some kind of push messages when service issues/updates are pending.


That would be wonderful. SmartThings does a great job with that. I get text updates as well.


I don’t disagree, but from my point of view development efforts should be prioritized to stabilize known issues, fix known bugs, and get promised features working. Development of a dashboard would be great, but could be mitigated by better communication from the GF team in the interim.


Happy Birthday @jbpa! :grinning:


Same issue here. Worked on Wednesday great, Thursday could never get it to calibrate, Friday worked again, Sunday says offline. Nothing has changed on my end. DO YOU HAVE TOO MANY PEOPLE HITTING THE SERVER? I’d pay money for software I could move locally to avoid the online raster. I’m wondering if you are a victim of your own success.


Transparency is important. There are plenty of easy ways to provide this. is quite good, very cheap, and very popular. It’s used by Dropbox, Twilio, New Relic, Reddit, Fastly, Vimeo, … you get the idea. Not only does it make uptime visible (which speeds troubleshooting and earns credibility), it can send out customer alerts, coordinate planned outages (for upgrades, etc.) and feed outages into internal ops tools.


No disagreement from me. But, when you’re working with limited resources, you have to prioritize. I just think core functionality should be that priority right now.


In my experience, investing a little effort in tools like this leads to a huge time savings in troubleshooting. And we’re not talking about a lot of time, for getting basic uptime monitoring in place.


Thanks for the suggestion! I’ll make sure the team gets it.

It looks like you’ve been able to connect and print since starting this thread. If this issue reoccurs, please start a new thread or send an email to