Comments

• rpqu Member

  August 3

  First
• zGato Member

  August 3

  can you stop ignoring the questions in your other threads?

  Thanked by 9Killix oloke tzuli Nekopara KeyGenMe forest buggedout Xrmaddness Porlam
• JohnFilch123 Member

  August 3

  I guess can be used for CH location @forest not ideal but well
• forest Member

  August 4 edited August 4

  @JohnFilch123 said:
  I guess can be used for CH location @forest not ideal but well

  For CH I'm actually going with @PacketraOliver. They aren't cheap but they have a good network.

  @zGato said:
  can you stop ignoring the questions in your other threads?

  Have you been receiving any more false positive warnings? So far I haven't but I can't tell if that's because he disabled them for everyone, disabled them for just me, or adjusted the thresholds. Or maybe I'm just getting lucky.

  @antonpa The only thing that's been holding me back from buying more of your VPSes is the uncertainty surrounding whether I can keep running Tor middle nodes and Globalping probes. I hope you can talk with us.

  Thanked by 3oloke JohnFilch123 PacketraOliver
• zGato Member

  August 4 edited August 4

  @forest said:

  @zGato said:
  can you stop ignoring the questions in your other threads?

  Have you been receiving any more false positive warnings? So far I haven't but I can't tell if that's because he disabled them for everyone, disabled them for just me, or adjusted the thresholds. Or maybe I'm just getting lucky.

  @antonpa The only thing that's been holding me back from buying more of your VPSes is the uncertainty surrounding whether I can keep running Tor middle nodes and Globalping probes. I hope you can talk with us.

  For now nope, but I'd rather get a proper statement by @antonpa himself of what they're doing next.

  Last abuse report is from July 26th

  Thanked by 1forest
• antonpa Member, Patron Provider

  August 10

  @zGato Thanks for bringing this up. We’re currently working on improving and fine-tuning our systems, and we’d like to take a closer look at your case with our engineers to understand what happened.

  Could you please send us your service ID(s) and client ID? We’ll check everything on our side.

  Also, while we’re working on this, we plan to extend the abuse notice dispute window from 24 to 72 hours, so customers have more time to respond

  Thanked by 1tzuli
• antonpa Member, Patron Provider

  August 10

  @forest said: Have you been receiving any more false positive warnings? So far I haven't but I can't tell if that's because he disabled them for everyone, disabled them for just me, or adjusted the thresholds. Or maybe I'm just getting lucky.

  >

  @forest Thanks for explaining your concerns so clearly and for your patience.
  We have the information about what was running on your VPS and your service details. Our engineers will review the cases and check what exactly triggered the warnings.
  We are working on improving and tuning our systems, and we’ll make sure to investigate the root cause rather than just the symptoms.
  In the meantime, we plan to extend the abuse notice dispute window from 24 to 72 hours, so customers have enough time to respond before any action is taken on a service.

  Thanked by 1tzuli
• zGato Member

  August 10 edited August 10

  @antonpa said:
  @zGato Thanks for bringing this up. We’re currently working on improving and fine-tuning our systems, and we’d like to take a closer look at your case with our engineers to understand what happened.

  Could you please send us your service ID(s) and client ID? We’ll check everything on our side.

  Also, while we’re working on this, we plan to extend the abuse notice dispute window from 24 to 72 hours, so customers have more time to respond

  For example one from yesterday: service #919473. (ID U208708). I host RIPE Atlas & Globalping probes on all my servers and I have no plans on stopping, as this system makes no sense. I'd rather cancel all my servers and move on. This is the first provider I've ever encountered such behavior of mass customer scanning, besides Hetzner.

  This abuse report was for "Outbound Brute-Force" for SSH port to 144.31.234.73. You know the fun part? This server is blocked in Russia because someone was running a VPN server on it, and I can't even SSH it.
  
  

  Thanked by 1tzuli
• zed Veteran

  August 10

  i don't have anything constructive to add but i wanted to share how amused i am by this nonsense, lol.

  Thanked by 4zGato Nekopara Killix oloke
• zGato Member

  August 10 edited August 10

  @forest they do actually suspend servers btw, I have 2 servers down for getting two "abuse" reports in a row. (or they're in the same hostnode and they're both down lol)
• forest Member

  August 10 edited August 10

  @zGato said: This is the first provider I've ever encountered such behavior of mass customer scanning, besides Hetzner.

  Many providers actually do this kind of scanning, but they aren't configured nearly as strictly and so have few if any false positives. It's usually nothing more than watching out for sinkhole IPs and IPs from known botnets.

  @zGato said:
  @forest they do actually suspend servers btw, I have 2 servers down for getting two "abuse" reports in a row. (or they're in the same hostnode and they're both down lol)

  Did 24 hours pass since the initial report before they were suspended? Because I've gotten as many as 4 (I think) reports stacked up on the same service in a row before I got to replying to them, but I did reply to them before 24 hours elapsed.
• forest Member

  August 10

  @antonpa said: @zGato Thanks for bringing this up. We’re currently working on improving and fine-tuning our systems, and we’d like to take a closer look at your case with our engineers to understand what happened.

  I would be happy to give a detailed technical explanation that will be understood by you and your engineers if you would like (I know the exact problem and solution), but I want to be sure it is listened to and not dismissed.

  I have not had any warnings recently, but I do not know if that is because you changed some settings on your filter. I did not make any changes on my side.

  Could you please send us your service ID(s) and client ID? We’ll check everything on our side.

  Client ID is U290929. Service IDs are 1215053-290929, 1075861-290929, 1082985-290929, and 1093795-290929.

  @zGato said:
  @forest they do actually suspend servers btw, I have 2 servers down for getting two "abuse" reports in a row. (or they're in the same hostnode and they're both down lol)

  @antonpa Could you please look into this as well? @zGato is not an abuser.

  Thanked by 1zGato
• Killix Member

  August 10 edited August 10

  @antonpa said:
  @zGato Thanks for bringing this up. We’re currently working on improving and fine-tuning our systems, and we’d like to take a closer look at your case with our engineers to understand what happened.

  Could you please send us your service ID(s) and client ID? We’ll check everything on our side.

  Also, while we’re working on this, we plan to extend the abuse notice dispute window from 24 to 72 hours, so customers have more time to respond

  1130886-313636 (currently 3 open abuse reports)

  Currently, no abuse reports, but recently:
  1120312-300200
  1113007-300200
  1098328-300200

  On the VPS runs I2P, Syncthing Relay and Snowflake.

  Thanked by 1zGato
• antonpa Member, Patron Provider

  August 11

  I would be happy to give a detailed technical explanation that will be understood by you and your engineers if you would like (I know the exact problem and solution), but I want to be sure it is listened to and not dismissed.

  @forest It will definitely be reviewed. We will analyze your explanation together with our engineers and get back to you within this week.
  Thank you for providing the details — we appreciate your help in understanding the issue and finding the right solution.