Charged for Public IP Address

It appears you're experiencing an issue with a public IP address that's incurring charges but isn't visible in the usual places. This can be a frustrating situation, but there are a few steps you can take to address it:

1. Delayed billing updates: Keep in mind that AWS billing data typically takes 2-3 days to be fully consolidated and displayed in your account. If you've recently made changes, it may not be reflected immediately in your charges.

2. Check all regions: Ensure you've looked for Elastic IPs in all AWS regions, not just your primary one. Sometimes, IPs can be allocated in regions you don't typically use.

3. Other services using public IPs: Remember that charges for public IPv4 addresses can apply to services beyond EC2, such as Global Accelerator endpoints or site-to-site VPNs. These might not show up in the Elastic IP section.

4. Use Cost Explorer: To track your public IP charges more precisely, use AWS Cost Explorer. Filter for usage types containing "PublicIPv4:InUseAddress" or "PublicIPv4:IdleAddress" to see if charges are continuing and from which specific resources.

5. Check for reverse DNS records: In some cases, particularly with Lightsail static IPs, a reverse DNS record may be associated with the IP address, preventing you from releasing it and continuing to incur charges.

Given that you can see the IP in Amazon VPC IP Address Manager but not in the Elastic IP section, and there's no network interface attached, this could indicate a stuck or orphaned resource. In this case, the best course of action would be to contact AWS Support. They can provide a more detailed analysis of your account, help identify any hidden or stuck resources that might be causing these charges, and assist in releasing or removing the problematic IP address.

Remember, as of February 1, 2024, AWS charges $0.005 per hour for public IPv4 addresses, regardless of whether they are attached to a running instance or not. It's important to resolve this issue to avoid ongoing unnecessary charges.
  

Sources
I am getting Charged for unattached static IP, But unattached static IP already deleted | AWS re:Post
How to ensure that I no longer use a public IPv4 address | AWS re:Post