Hey folks, aside from our previous post hopefully you haven’t noticed (because we’re putting a lot of effort into you not being impacted) that the Glitch platform has been under significant strain from abusive traffic for the last two weeks or so. We’ve put some mitigations in place and are working on a more persistent, manageable, and less chaotic process and configuration. We’ve had a lot of assistance and support from elsewhere at Fastly - to be quite honest I’m not sure we’d come out the other side of this the same Glitch we are today if not for the help and capabilities we have at our disposal now; my personal and heartfelt thanks go out to the larger Fastly organization for helping to keep us together and to alleviate the stress on our over-taxed engineering team.
We’ll be making more changes in the coming days, and our priority is to ensure your projects stay operational and performant. That said, given how fundamental some of the updates are, some inevitable bumps in the road may impact Glitch services.
As I’ve mentioned before, these sorts of events (and the smaller-but-still-disruptive day-to-day operational challenges we face) function to keep us from working on the features and fixes we (and we hope you) are looking forward to. Being part of Fastly really pays off when we experience novel or particularly sophisticated challenges in building and scaling Glitch and today I’m confident that we’re forging a path that will alleviate some of that toil for us and grant us the space we need to complete some long-awaited updates.
I don’t think we’re in a place to offer any hard commitments today, but my expectation is that soon you’ll see us move forward at a pace we haven’t been able to sustain for a long time. What exactly that means for Glitch is something we’re working hard to figure out as a team, and I hope you’ll be here with us to see the fruits of all of this labor.
Cheers, and thanks for taking this journey with us;
cori