Member OP
Hey wey so I got this uptime thing going on Contabo right? Uptime robot pinging every 30 seconds and they just sent me this angry ticket saying im doing ddos attack on their own infrastructure wey! Like its their own ip how is monitoring a ddos? Now my vps is throttled and my project is down. Anyone else got this problem or is Contabo just braindead?
Member
This is what happens when someoneelses Monitoring policy collides with someoneelses Abuse automation[1]. The Providers have outsourced their brains to scripts that count Packets per second and panic. Back in 2015 this never happened because humans read tickets. Now you get Algorithmic justice and your legitimate HealthChecks become a DenialOfService in their spreadsheet. Contabo is hardly alone here[2]. Every BudgetHost runs the same cheap heuristics. The real issue is your Probe frequency—thirty seconds is aggressive by modern standards where five minutes is the new normal. Youre not wrong, but youre also not going to win against the FilterRules. Footnotes: [1] see my thread on TheDeathOfTier1Support. [2] Hetzner did the same to me last quarter.
Just use smokeping bro. Or better yet, skill issue
Seriously though, 30 second intervals from a single source? Thats not monitoring, thats anxiety with a cron job. Drop it to 5 minutes like Berlin1 said, or run your own smokeping on a $3 oracle box and stop begging Contabo to understand tcp. Their abuse team probably thinks ICMP is a hacking tool.
Contabo can whitelist one lah. Just open ticket say monitoring ip leh. I done before with OVHcloud, they add to exception list already. No need change interval also can. But if you lazy to ask then 5 minutes lor. Your choice.
These days its all saas monitoring with 47 different cloud endpoints hitting your provider from every angle, so I get why the mitigation triggers. Still, Contabo should have a published whitelist process. Back then you called a human and it was fixed in ten minutes.
What does the ticket actually cite? Their AUP clause or just automated counts?
Same thing happened to me on a different host, 60 second pings got flagged.
