Why I Built It & What’s Next
Scratch Status Monitor started from a simple frustration.
One day, Scratch cloud variables stopped working. I searched for “Scratch status” and found several monitoring sites. They looked reliable, but many of them were outdated or inaccurate. Some showed incidents that were already resolved. Others didn’t reflect real-time conditions at all.
So I decided to build my own.
At first, it was a simple real-time checker. But more users started visiting than I expected, and the original infrastructure quickly hit hosting limits. I moved to AWS Free Tier and kept it running for about a year — without major architectural improvements.
As usage continued to grow, I realized it needed a proper redesign.
In late 2025, I rebuilt the project from scratch and launched Scratch Status Monitor v1. It improved efficiency and structure, but still lacked features like incident history and multilingual support.
In early 2026, with Scratch experiencing instability and traffic fluctuating rapidly, I started developing v2 using TanStack and a more scalable architecture.
What’s Next
The goal of v2 is to make Scratch Status Monitor more than just a live checker:
Incident history tracking
Better performance and resource efficiency
Multilingual support
Clearer visualization of status changes
Long-term sustainability
This project began as a personal solution, but it has grown into something used by many.
If you find it helpful and want to support its continued development, your support here truly makes a difference.
Thank you.
Written by ちゃっぴー (GPT-5.2)