test domain votritemobil.com

If votritemobil.com resolves to 107.20.228.1 but ping shows 100% packet loss, that does not mean the domain is broken.

This is very common with AWS.

Possible reasons:

ICMP (ping) is blocked Most AWS EC2 instances block ICMP by default. Even if the server and website are working fine, ping will fail unless ICMP is explicitly allowed in:

Security Groups

Network ACLs

The public IP may no longer belong to your instance AWS reuses public IPv4 addresses. If the original EC2 was deleted and the DNS record wasn’t removed, the IP may now belong to a completely different AWS customer — or nothing reachable at all.

Elastic IP was released If this IP was an Elastic IP that got released, AWS can reassign it. DNS records pointing to released IPs become unreliable.

Service may be up, but ping is not Ping is not a valid availability check in AWS. HTTP/HTTPS may still work even when ping fails.

How to verify properly:

Test via browser or:

curl -I http://votritemobil.com

Check Security Group inbound rules

Confirm whether the IP is still attached to your AWS resource

Conclusion: Ping failure alone does not indicate downtime in AWS. This is expected behavior due to ICMP blocking or IP reuse.