Storm Passed, Shields Up!
A quick word about yesterday’s hiccup, what we fixed, and how we’re protecting your uptime
Hi everyone,
If you tried to hit our API yesterday, you may have noticed a rash of 503 errors or unusually slow responses, even a complete down service. The short story: a spam botnet discovered our legacy endpoints and fired millions of junk requests in just a few minutes. Our automatic defenses throttled traffic, but the surge was big enough that we chose to pull the emergency brake, patch the gates, and bring everything back up in a controlled way.
What actually happened?
- Massive request spike — far above normal usage — hammered v1 and legacy URLs.
- Our rate-limiter kicked in, but some nodes still choked, leading to intermittent outages.
- We temporarily throttled all traffic while we traced and blocked the offenders.
Important: No customer data leaked, no credits were lost, and the core database was never at risk. It was simply an overload.
What we’ve done since
- Upgraded our Web Application Firewall (WAF) to spot and drop similar floods in real time.
- Refined rate-limiting rules so bad actors get cut off faster while legit users sail through.
- Added burst buffers on the legacy endpoints, giving them extra headroom before throttles trigger.
Everything is now back online, speeds are normal, and we’re monitoring the gauges 24/7.
How this affects you
- No action required. Your keys, hits, and integrations remain exactly as they were.
- Improved resilience. Future spam waves should fizzle out long before they touch your app.
- Transparent status. If something ever wobbles, you’ll see it first at https://status.freegoldprice.org.
One more thing—thanks for your patience ❤️
We know downtime is a pain, especially when you’re shipping features or running live dashboards. We’re sorry for the rough patch and grateful for the heads-up emails that helped us zero in on the culprit.
Questions or concerns? Hit us up at support@freegoldprice.org. Otherwise, enjoy the smooth skies — and stay golden! ✨