HAZI.ro | 25% LIFETIME VPS/VDS Servers | Extra IPs 0.75€/mo

FlorinMarian

Hello, dear community!

We offer a 25% recurring discount for all virtual private & dedicated servers if you use the discount code SUMMER-SUN (Other servers available on our website).

VDS - 2vCPU - 4GB RAM - 120GB SSD Enterprise

• 2x Dedicated vCPUs 2.30GHz ↗ 3.60GHz
• 4GB RAM DDR4 ECC 2133MHz
• 120GB SSD Enterprise RAID10
• 1Gbps Connection (Shared)
• Unlimited Monthly Traffic (10TB @1Gbps then Unlimited @100MBps)
• Voxility 1Tbps AntiDDoS Protection
• Price: 5.25 EUR/mo
• Purchase it here

KVM RO-1CPU-6GB-2x300GB

• 1x vCPU 2.30GHz ↗ 3.60GHz (1/2 Dedicated)
• 6GB RAM DDR4 ECC 2133MHz
• 2x 300GB Seagate Enterprise 7200rpm
• 1Gbps Connection (10Gbps Shared)
• Unlimited Monthly Traffic (10TB @1Gbps then Unlimited @100MBps)
• Voxility 1Tbps AntiDDoS Protection
• Price: 6.75 EUR/mo
• Purchase it here

Physical servers:

Server 1:

• CPU: 2x E5-2698 V3 32 Cores / 64 Threads (2.30GHz ↗ 3.60GHz)
• Memory: 16x 16GB RAM DDR4 ECC 2133MHz
• Storage SSD: 2x Samsung 860 EVO 1TB + 2x Samsung PM893 Enterprise 1.92TB + 44TB SATA Enterprise 7200rpm (12 Drives)
• Network: 1x 10Gbps
• Protection: Voxility 1Tbps AntiDDoS

Server 2:

• CPU: 2x E5-2699 V3 36 Cores / 72 Threads (2.30GHz ↗ 3.60GHz)
• Memory: 12x 16GB RAM DDR4 ECC 2133MHz
• Storage SSD: 4x Samsung PM893 Enterprise 1.92TB
• Network: 4x 1Gbps
• Protection: Voxility 1Tbps AntiDDoS

Service features:

• Dedicated Physical Thread per vCPU
• KVM Virtualization
• NoVNC Console Access
• Integrated Control Panel
• 1-click Operating System Installation
• Intrusion Prevention System
• Intrusion Detection System

Operating Systems:

• CentOS 7 64bits
• CentOS 8 64bits
• CentOS 9 64bits
• Debian 9 64bits
• Debian 10 64bits
• Debian 11 64bits
• Ubuntu 18.04 64bits
• Ubuntu 20.04 64bits
• Ubuntu 22.04 64bits
• FreeBSD 12.x 32bits
• FreeBSD 12.x 64bits
• FreeBSD 13.x 32bits
• FreeBSD 13.x 64bits

Useful information:

Looking Glass: Click here
Terms & Conditions: Click here
Accetable Usage Policy: Click here
Privacy Policy: Click here

Accepted payment methods:

• MobilPay (Visa / Maestro / Mastercard)
• Paysafecard
• Bitcoin
• Ethereum
• USD Coin
• Dogecoin
• Litecoin
• Dai
• Bitcoin Cash
• Bank Transfer

yoursunny

A single YABS triggers "permanent mitigation" that your network speed would decrease to less than 20 Mbps.
A single "abuse", including zero day attack that is not your fault, causes service deletion with 30-minute notice and no second chances.

Also, IPv6 and push-up payment method are missing.

jcolideles

@yoursunny said:
A single YABS triggers "permanent mitigation" that your network speed would decrease to less than 20 Mbps.
A single "abuse", including zero day attack that is not your fault, causes service deletion with 30-minute notice and no second chances.

Also, IPv6 and push-up payment method are missing.

Thanks for the heads-up.

bulbasaur

@yoursunny said: A single YABS triggers "permanent mitigation" that your network speed would decrease to less than 20 Mbps.

The original complaint thread seems to have had a negative effect on your "brotherhood."

Thanked by @FlorinMarian

I don't think you know what thanking a post really means.

FlorinMarian

@stevewatson301 said:

@yoursunny said: A single YABS triggers "permanent mitigation" that your network speed would decrease to less than 20 Mbps.

The original complaint thread seems to have had a negative effect on your "brotherhood."

Thanked by @FlorinMarian

I don't think you know what thanking a post really means.

Being frustrated isn't a good choice when doing business.

yoursunny

@stevewatson301 said:

@yoursunny said: A single YABS triggers "permanent mitigation" that your network speed would decrease to less than 20 Mbps.

The original complaint thread seems to have had a negative effect on your "brotherhood."

Nigh Sect, destroying brotherhood since 2021.

spiritysdx

@yoursunny said:
A single YABS triggers "permanent mitigation" that your network speed would decrease to less than 20 Mbps.
A single "abuse", including zero day attack that is not your fault, causes service deletion with 30-minute notice and no second chances.

Also, IPv6 and push-up payment method are missing.

You are right, He said that I abnormally requested the IP 221.179.155.161

riofredinand

@spiritysdx said:

@yoursunny said:
A single YABS triggers "permanent mitigation" that your network speed would decrease to less than 20 Mbps.
A single "abuse", including zero day attack that is not your fault, causes service deletion with 30-minute notice and no second chances.

Also, IPv6 and push-up payment method are missing.

You are right, this also includes using speedtest's CLI for speed testing, which is also not allowed. At present, my server has been permanently suspended and my account cannot be used.

Great you successfully stop me. I assume it's pay to close.

spiritysdx

@riofredinand said:
Great you successfully stop me. I assume it's pay to close.

He said I was wrong, that IP address is not the IP address of speedtest. My confirmation was wrong. I queried the detailed data of the IP. It was generated by mobile phone traffic. I have not requested this address in my memory, and I have no way of knowing the reason for the request.

FlorinMarian

Let me know which SpeedTest CLI sends via NMAP 72 ping requests per second.
https://pastebin.com/ewWcpRJz

spiritysdx

@riofredinand said:
Great you successfully stop me. I assume it's pay to close.

I'm talking to customer service on a ticket and waiting for the final result.

NoComment

@spiritysdx said:

@riofredinand said:
Great you successfully stop me. I assume it's pay to close.

He said I was wrong, that IP address is not the IP address of speedtest. My confirmation was wrong. I queried the detailed data of the IP. It was generated by mobile phone traffic. I have not requested this address in my memory, and I have no way of knowing the reason for the request.

From your previous thread:

Then I use lxd to virtualize 6 small lxc containers on the server for my friends to use, and they will use python or golang to write scripts on them for testing.

Maybe your friends got your server compromised. Maybe your friends did the requesting. Who knows?

spiritysdx

@FlorinMarian said:
Let me know which SpeedTest CLI sends via NMAP 72 ping requests per second.
https://pastebin.com/ewWcpRJz

I was asking for the specific time of the request for investigation. I ran the speedtest program in the first hour of getting the server to measure the speed, and the follow-up information was followed up in the work order.

spiritysdx

@NoComment said:

@spiritysdx said:

@riofredinand said:
Great you successfully stop me. I assume it's pay to close.

He said I was wrong, that IP address is not the IP address of speedtest. My confirmation was wrong. I queried the detailed data of the IP. It was generated by mobile phone traffic. I have not requested this address in my memory, and I have no way of knowing the reason for the request.

From your previous thread:

Then I use lxd to virtualize 6 small lxc containers on the server for my friends to use, and they will use python or golang to write scripts on them for testing.

Maybe your friends got your server compromised. Maybe your friends did the requesting. Who knows?

I didn't use lxc to virtualize anything this time.

FlorinMarian

@spiritysdx said:

@FlorinMarian said:
Let me know which SpeedTest CLI sends via NMAP 72 ping requests per second.
https://pastebin.com/ewWcpRJz

I was asking for the specific time of the request for investigation. I ran the speedtest program in the first hour of getting the server to measure the speed, and the follow-up information was followed up in the work order.

Time is on first column on that pastebin 19:17:32.microseconds

spiritysdx

@FlorinMarian said:
Time is on first column on that pastebin 19:17:32.microseconds

UTC?

FlorinMarian

@spiritysdx said:

@FlorinMarian said:
Time is on first column on that pastebin 19:17:32.microseconds

UTC?

UTC+2 [RO local time]

corbpie

25% off isn’t the 40% off you are specifying

FlorinMarian

@corbpie said:
25% off isn’t the 40% off you are specifying

Oh..God!
I forgot to replace percent (replaced only URLs + Product price from old thread).
I'll be happy if someone from Moderation Team can edit that percent for me.
Thank you!

NoComment

@spiritysdx said:

@NoComment said:

@spiritysdx said:

@riofredinand said:
Great you successfully stop me. I assume it's pay to close.

He said I was wrong, that IP address is not the IP address of speedtest. My confirmation was wrong. I queried the detailed data of the IP. It was generated by mobile phone traffic. I have not requested this address in my memory, and I have no way of knowing the reason for the request.

From your previous thread:

Then I use lxd to virtualize 6 small lxc containers on the server for my friends to use, and they will use python or golang to write scripts on them for testing.

Maybe your friends got your server compromised. Maybe your friends did the requesting. Who knows?

I didn't use lxc to virtualize anything this time.

If you are sure you didn't do this and @FlorinMarian didn't mistake you for someone else, then congrats. You got yourself compromised in less than a day. Most likely, you are running some script you shouldn't be running.

DP

@FlorinMarian said:

@corbpie said:
25% off isn’t the 40% off you are specifying

Oh..God!
I forgot to replace percent (replaced only URLs + Product price from old thread).
I'll be happy if someone from Moderation Team can edit that percent for me.
Thank you!

spiritysdx

Here's a link to what I did in the first few hours I got the server, I'll list it here
https://hub.docker.com/r/peer2profit/peer2profit_x86_64
https://hub.docker.com/r/traffmonetizer/cli
https://github.com/zq/superspeed
If you say I did something before that time period that caused the abnormal request, it could only be caused by one of the above links.

EDIT: Should also add https://github.com/zhanghanyun/backtrace, that's why that IP is being requested.

spiritysdx

At the time you mentioned, I only got the machine for about an hour and a half. I actually only performed the operation in the first hour of getting the server, and the subsequent operation was 6~7 hours later.

NoComment

@spiritysdx said:
Here's a link to what I did in the first few hours I got the server, I'll list it here
https://hub.docker.com/r/peer2profit/peer2profit_x86_64
https://hub.docker.com/r/traffmonetizer/cli
https://github.com/zq/superspeed
If you say I did something before that time period that caused the abnormal request, it could only be caused by one of the above links.

Dude, I'm not even gonna bother. That looks like traffic exchange and I am not surprised your previous provider kicked you out.

This guy's previous thread should be updated to mention that he was probably running traffic exchange so it's fair to the provider.

spiritysdx

Well, it looks like the cause of everything is me.

bulbasaur

@spiritysdx said:
Well, it looks like the cause of everything is me.

It certainly is. A lesson to learn.

spiritysdx

@NoComment said:

@spiritysdx said:
Here's a link to what I did in the first few hours I got the server, I'll list it here
https://hub.docker.com/r/peer2profit/peer2profit_x86_64
https://hub.docker.com/r/traffmonetizer/cli
https://github.com/zq/superspeed
If you say I did something before that time period that caused the abnormal request, it could only be caused by one of the above links.

Dude, I'm not even gonna bother. That looks like traffic exchange and I am not surprised your previous provider kicked you out.

This guy's previous thread should be updated to mention that he was probably running traffic exchange so it's fair to the provider.

I checked it again, He said that I abnormally requested the IP 221.179.155.161 , I checked that this address is indeed the speed measurement address of speedtest, so it is not caused by traffic exchange, it is caused by the speed measurement I performed speedtest, related The IP information will be pasted later.

spiritysdx

https://github.com/zhanghanyun/backtrace
The collection script I used, the script used for backhaul routing, and the address you mentioned in the screenshot.

spiritysdx

https://github.com/zhanghanyun/backtrace/blob/main/asn.go
221.179.155.161

rIp   = []string{"219.141.136.12", "202.106.50.1", "221.179.155.161", "202.96.209.133", "210.22.97.1", "211.136.112.200", "58.60.188.222", "210.21.196.6", "120.196.165.24"}
 rName = []string{"北京电信", "北京联通", "北京移动", "上海电信", "上海联通", "上海移动", "广州电信", "广州联通", "广州移动"}
 ca    = []color.Attribute{color.FgHiBlue, color.FgHiMagenta, color.FgHiYellow, color.FgHiGreen, color.FgHiCyan, color.FgHiRed, color.FgHiMagenta, color.FgHiYellow, color.FgHiBlue}
 m     = map[string]string{"AS4134": "电信163 [普通线路]", "AS4809": "电信CN2 [优质线路]", "AS4837": "联通4837[普通线路]", "AS9929": "联通9929[优质线路]", "AS9808": "移动CMI [普通线路]", "AS58453": "移动CMI [普通线路]"}

NoComment

@spiritysdx said:
https://github.com/zhanghanyun/backtrace
The collection script I used, the script used for backhaul routing, and the address you mentioned in the screenshot.

You are indeed right but at this point it is questionable if @FlorinMarian is happy with traffic exchange customers. It probably isn't a problem with "dedicated cpu" and "unmetered bandwidth" but some providers don't like traffic exchange.

spiritysdx

@NoComment said:

@spiritysdx said:
https://github.com/zhanghanyun/backtrace
The collection script I used, the script used for backhaul routing, and the address you mentioned in the screenshot.

You are indeed right but at this point it is questionable if @FlorinMarian is happy with traffic exchange customers. It probably isn't a problem with "dedicated cpu" and "unmetered bandwidth" but some providers don't like traffic exchange.

The reason for blocking my server is wrong, and I accept what you say, but I should state the facts. The merchant did not block my server for the reason you said.