Costs charge for a vpn endpoint that does not exist

It's understandable that you're concerned about being charged for a VPN endpoint that you believe no longer exists. This situation can occur due to a few reasons:

1. Delayed billing updates: Sometimes, there can be a delay between when you delete a resource and when it stops appearing on your bill. AWS billing systems may take a day or two to fully reflect changes.

2. Lingering associated resources: Even if you've deleted the main VPN endpoint, there might be related resources still active, such as Elastic IP addresses or network interfaces that were associated with the VPN.

3. Cross-region resources: Ensure you've checked all AWS regions for any remaining VPN-related resources, as they might exist in a region you don't typically use.

To address this issue:

1. Use AWS Cost Explorer to analyze your costs in detail. Set the granularity to "daily" and group by "usage type" or "API operation" to see exactly what VPN-related charges are occurring.

2. Double-check all regions in your AWS account for any forgotten or unused VPN resources.

3. Look for and release any unnecessary Elastic IP addresses, as these can incur charges even when not attached to active resources.

4. Review your account for any lingering network interfaces or other VPC components that might be related to the former VPN endpoint.

5. If you're still unsure, consider using AWS Trusted Advisor for a more comprehensive review of your account resources.

If after taking these steps you still see unexpected charges, it would be advisable to contact AWS Support directly. They can provide a more detailed analysis of your account's usage and billing history, and help identify any hidden resources or potential billing errors.

Remember, while creating and using a VPC itself doesn't incur charges, certain VPC-related components and features do have associated costs. It's important to regularly review and manage your AWS resources to optimize costs.
Sources
Having issue with billing. | AWS re:Post
Billing regarding my vpc | AWS re:Post
Logically Isolated Virtual Network - Amazon VPC Pricing - Amazon Web Services

In the cost explorer I can see the daily charge due to usage type "EUC1-ClientVPN-EndpointHours (Hrs)" in region EU Frankfurt (eu-central-1) but there isn't any vpn endpoint in this region since several days. I can't understand how it can be possible.