16 days ago
This is yet another time this issue has occurred 😠,
temporarily disrupting our production environment. Our users are once again encountering this problem in production.
We already provided feedback after the previous incident, but we did not receive any response.
not even an acknowledgment or apology.
https://discord.com/channels/713503345364697088/1471172506260996238
I understand that no one intends for this to happen.
However, this must stop impacting our production environment. Please take immediate action to prevent this from happening again.
14 Replies
16 days ago
Hello,
It seems like our changelog announcing DDoS protection has provoked someone, and since we are still establishing a baseline with Fastly, full DDoS mitigations weren't applied.
Now our services have fully recovered. However, the damage has already been done. our users experienced the disruption.
This product is built on trust, and incidents like this directly affect that trust. We are concerned about the impact this has had on our users and the confidence they place in our service.
Thank you.
I'm getting the same error; I'm assuming (and hoping) it's related as well
16 days ago
it is becoming a daily theme! same here
16 days ago
Hi there, it's a DDoS attack pattern. We were establishing a basline with Fastly hence why we didn't have full mitigations.
16 days ago
Is it possible to disable DDoS protection from Fastly per services?
16 days ago
For those who use cloudflare, removing the proxy from dns mitigate a little.
But yeah, still a problem 
at least the 429
16 days ago
Rather, it's the fact that it wasn't fully out, we have gotten it back. The attack is mitigated. Sorry for the impact again.
16 days ago
It is not. Curious why you ask?
16 days ago
I already have it enabled through my clouflare proxy
16 days ago
It might seem unnecessary, and maybe it is, but in practice, it's really not going to hurt anything to have it twice.
I recall reading a thread suggesting that certain Cloudflare DDoS rules should be turned off. I'm seeking clarification because I am seeing excessive access attempts to .php files. Previously, Cloudflare was blocking this and traffic was lower, but now I see HTTP logs again. The source IPs appear to be from fastly.com. Should I disable Cloudflare, or how should I adjust it?
Attachments
16 days ago
Fastly isn't going to block bot traffic, they are for DDoS so if this bot is not making excessive requests relative to an attack they will be let through.
Status changed to Solved brody • 16 days ago