Hi @f0o, you should definitely not just accept this. Can you share more information either here or in the ticket about the block? How exactly did you notice that you are blocked? Is there any error? Are you able to login? etc.
With this information, we can check what the issue might be or if you indeed are blocked.
Well at first I noticed that an update I made via GitHub didn’t trigger the Pages.
After looking at it through the dashboard I noticed I hadn’t stopped my cronjob to feed the cloudflare-runner PoC repo every 20 minutes with a job which likely added me to the abuse-list as I was effectively hogging a machine continuously…
When I then finally revoked access to that repo and disabled build (paused deployments) to further abuse the system I also noticed that scheduling new builds would yield a HTTP 400 response with JSON Payload:
"message": "Account has been blocked"
So my assumption is that during the Pages maintenance you guys noticed my cloudflare-runners and put me on the NoFly list - Which to be fair, is more than legit and entirely my own fault for forgetting to turn off builds after the initial PoC passed. (Assumption based on the coincidental timelines)
So that leads me to here now
On the up side, I moved the domain to a new (personal) account and noticed that it resolved the issue…
Which leads to further ways of abuse unfortunately.
Even though this is effectively a foot-bullet to me I’d suggest blacklisting Page builds per GitHub Integration Token since I was able to circumvent the Block by just using a different CloudFlare account without unlinking/relinking the GH Application.
Thanks for the quick reply. The error code is helpful and helps confirm that this is indeed on our end. Thanks a lot for being honest and I’d recommend putting this information into your ticket. I’ll reopen your ticket in a couple of minutes.