All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Vmiss configured the wrong MTU, leading to network issues.
After a DDoS incident, Vmiss set an incorrect MTU, causing node communication failures and service disruption (logs available). Admitting some impact yet denying any network issue, they are violating the SLA by refusing compensation.
[root@VM61689C735AF0576 ~]# timeout 5 tracepath www.google.com
1?: [LOCALHOST] pmtu 1500
1: no reply
[root@VM61689C735AF0576 ~]# timeout 5 tracepath www.github.com
1?: [LOCALHOST] pmtu 1500
1: no reply
[root@VM61689C735AF0576 ~]# timeout 5 tracepath www.youtube.com
1?: [LOCALHOST] pmtu 1500
1: no reply
[root@VM61689C735AF0576 ~]# timeout 5 traceroute www.google.com
traceroute to www.google.com (142.250.72.164), 30 hops max, 60 byte packets[root@VM61689C735AF0576 ~]#
[root@VM61689C735AF0576 ~]# timeout 5 traceroute www.github.com
traceroute to www.github.com (140.82.112.4), 30 hops max, 60 byte packets[root@VM61689C735AF0576 ~]#
Comments
what
how do you know its MTU issue?
sounds like you're being blocked entirely/nullrouted
None of this makes sense
No idea what makes you think its a MTU issue.
Because I identified that the default MTU of 1500 would affect access to certain networks, and VMiss also acknowledged this.
[root@VM61689C735AF0576 ~]# ip r | grep def
default via 216.40.85.1 dev eth0 proto static metric 100
[root@VM61689C735AF0576 ~]# ip a | grep -A 4 "eth0:"
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether d8:d5:d8:00:1d:cf brd ff:ff:ff:ff:ff:ff
altname enp0s17
altname ens17
inet 216.40.85.77/24 brd 216.40.85.255 scope global noprefixroute eth0
[root@VM61689C735AF0576 ~]# ping -c 3 -M do -s 1440 h5ai.soocoo.xyz
PING tnahost.soocoo.xyz (130.254.47.26) 1440(1468) bytes of data.
1448 bytes from mail.soocoo.xyz (130.254.47.26): icmp_seq=1 ttl=52 time=42.1 ms
1448 bytes from mail.soocoo.xyz (130.254.47.26): icmp_seq=2 ttl=52 time=42.3 ms
1448 bytes from mail.soocoo.xyz (130.254.47.26): icmp_seq=3 ttl=52 time=42.1 ms
--- tnahost.soocoo.xyz ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 42.118/42.185/42.293/0.076 ms
[root@VM61689C735AF0576 ~]# ping -c 3 -M do -s 1450 h5ai.soocoo.xyz
PING tnahost.soocoo.xyz (130.254.47.26) 1450(1478) bytes of data.
--- tnahost.soocoo.xyz ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2056ms
[root@VM61689C735AF0576 ~]# ping -c 3 -M do -s 1472 h5ai.soocoo.xyz
PING tnahost.soocoo.xyz (130.254.47.26) 1472(1500) bytes of data.
--- tnahost.soocoo.xyz ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2072ms
[root@VM61689C735AF0576 ~]#
Because I identified that the default MTU of 1500 would affect access to certain networks, and VMiss also acknowledged this.
[root@VM61689C735AF0576 ~]# ip r | grep def
default via 216.40.85.1 dev eth0 proto static metric 100
[root@VM61689C735AF0576 ~]# ip a | grep -A 4 "eth0:"
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether d8:d5:d8:00:1d:cf brd ff:ff:ff:ff:ff:ff
altname enp0s17
altname ens17
inet 216.40.85.77/24 brd 216.40.85.255 scope global noprefixroute eth0
[root@VM61689C735AF0576 ~]# ping -c 3 -M do -s 1440 h5ai.soocoo.xyz
PING tnahost.soocoo.xyz (130.254.47.26) 1440(1468) bytes of data.
1448 bytes from mail.soocoo.xyz (130.254.47.26): icmp_seq=1 ttl=52 time=42.1 ms
1448 bytes from mail.soocoo.xyz (130.254.47.26): icmp_seq=2 ttl=52 time=42.3 ms
1448 bytes from mail.soocoo.xyz (130.254.47.26): icmp_seq=3 ttl=52 time=42.1 ms
--- tnahost.soocoo.xyz ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 42.118/42.185/42.293/0.076 ms
[root@VM61689C735AF0576 ~]# ping -c 3 -M do -s 1450 h5ai.soocoo.xyz
PING tnahost.soocoo.xyz (130.254.47.26) 1450(1478) bytes of data.
--- tnahost.soocoo.xyz ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2056ms
[root@VM61689C735AF0576 ~]# ping -c 3 -M do -s 1472 h5ai.soocoo.xyz
PING tnahost.soocoo.xyz (130.254.47.26) 1472(1500) bytes of data.
--- tnahost.soocoo.xyz ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2072ms
[root@VM61689C735AF0576 ~]#
It may be because of anti ddos solutions using GRE, which requires you to have mtu less than 1476.
They did not suggest modifying the MTU, and I had to identify the issue myself through troubleshooting. Before I identified the problem, it continuously affected my service. VMiss does not admit that their network has issues and refuses to compensate for the downtime according to the SLA.
there is no downtime. you're still able to access the server.