a month ago
Hi,
My workspace was restricted with the reason "Suspicious activity detected." I'd like to understand why and get this resolved.
I deployed a small Node.js service (v2ray-sub-updater) that does the following:
- Fetches a text file from a single GitHub raw URL containing a list of proxy configuration entries.
- Opens short TCP connections (3-second timeout) to check whether each listed server address/port is reachable, using a concurrency limit of 50 simultaneous connections.
- Filters out unreachable entries and serves the remaining list as plain text on one HTTP endpoint.
The source list had around 56,000 entries, so the service made a large number of outbound TCP connection attempts to many different external IPs in a short time. I believe this is likely what triggered the suspicious activity flag, even though it wasn't intended as scanning or abuse - just a reachability check on a subscription list.
Could you please review this and let me know what's needed to lift the restriction? I'm happy to reduce the concurrency or rate-limit the checks going forward if that helps.
Thanks!
1 Replies
a month ago
We're not able to share the specifics behind why a workspace restriction was applied. There is no self-serve action that will lift this restriction, and upgrading or adding a payment method will not change it.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago