We want to acknowledge the past several weeks of service issues. Many of you have reached out thoughtfully and offered support. Thank you for that. You’re the reason why we have a reputation for being one of the friendliest communities of coders on the web!
Here’s what’s going on:
We’re continuing to grow at a really rapid pace, and also seeing new kinds of high-volume automated requests hitting the service. Handling both of those at the same time is straining the platform. In addition to all the increasingly-popular apps that community makers are creating, we’re also seeing an influx of attacks on our service and some projects running malicious code. These make the task at hand even more challenging. In the coming weeks, we’re going to be making significant changes that will have a big impact on uptime and stability. On top of that, we’re working on improving your experience with managing projects on Glitch.
To be clear:
Until we get through these changes, you can expect there to be some instability from time to time. We’re sorry for the inconsistent experience, and are working as quickly as we can to fix this in a way that will last. In the meantime, here’s what you can do if you are experiencing instability:
Keep an eye on status.glitch.com for updates. We’re making sure those updates are more timely and descriptive.
Send a message to email@example.com if you find your projects still aren’t loading once an incident is resolved.
Avoid making changes to a project if you start to see reconnecting errors. Changes to your code are only reliably stored when that connection is working