Unjustified VPC Endpoint Charges in ap-south-1 – How to Identify Source?

Hello AWS Community,

I’m seeing VPC Endpoint charges ($0.013 per hour) in ap-south-1 (Mumbai), even though I have deleted all VPC endpoints.

What I have already done:

Deleted all visible VPC Endpoints in ap-south-1 and verified none remain.

Checked all other AWS regions using both EC2 Console and CLI (aws ec2 describe-vpc-endpoints) – no active endpoints found.

Reviewed EC2 Network Interfaces for orphaned ENIs associated with endpoints – none found.

Cost Explorer shows usage type APS1-VpcEndpoint-Hours for the following endpoint IDs:

vpce-01b8391db2f72bff0 vpce-03f2d83d906a50f7a vpce-0663b78df1e77af4c vpce-0d42ac692421862f0

Attempts to delete these IDs via CLI return InvalidVpcEndpoint.NotFound.

Billing shows VpcEndpoint-Hours 328 hours ($4.26) for the month so far.

My questions:

How can I identify the exact resource or service consuming VpcEndpoint-Hours if the endpoint itself is deleted?

i had used vpcendpoint to connect to cloudwatch interface but later deleted the vpc endpoint and currently cloudwatch is showing stale logs and metric of the project i had created 3 days back whose ec2, vpc , vpcendpoint everything is deleted Are CloudWatch Logs or Metrics (or other AWS services) automatically provisioning hidden VPC Endpoints that continue to accrue charges?

Where can I find hidden interfaces, ENIs, or service-managed VPC endpoints that might be responsible?

Will deleting CloudWatch logs/metrics stop VPC Endpoint charges if they are associated with a hidden service endpoint?

I would appreciate guidance on how to permanently stop these charges and identify the source. If this is a billing anomaly, information about a credit adjustment would also be helpful.

Thank you!