I am still being charged for a AWS RDS even though i have deleted the database and any snapshots.

There are several reasons why you might still be seeing charges for RDS even after deleting the database and snapshots:

1. Resources in different regions: You might have overlooked resources in other AWS regions. When checking your bill, verify which region the RDS charges are coming from.

2. Hidden snapshots: Check all snapshot tabs in the RDS console, including automated backups that might have been created during deletion. Make sure to check all regions.

3. Delayed billing updates: Sometimes AWS billing can have a delay in reflecting changes. The charges you're seeing might be for usage incurred before deletion.

4. Backup storage: You might still have backup storage that exceeds the free allocation, which continues to incur charges.

To troubleshoot this issue:

• Use AWS Cost Explorer to identify exactly what RDS features are being charged. Filter by "Service" (select RDS) and "Dimension" (select "Usage Type") to see detailed information.

• Check Cost Explorer with daily granularity to better observe what you're spending money on.

• Verify all regions for any forgotten RDS resources, snapshots, or replicas.

• Look for any RDS proxies or other related services that might still be active.

If you still can't identify the source of the charges after these steps, contacting AWS Support through the "Account and billing" option would be the best course of action. They can help identify the specific resources causing the unexpected charges.
Sources
Why am I still losing money due to RDS, even though I stopped and deleted it? | AWS re:Post
Abnormal Billing from RDS | AWS re:Post
To stop RDS from billing | AWS re:Post
Why am I being charged money on my account? | AWS re:Post
I don't have anything on my RDS, but it costs me every month. | AWS re:Post

Apart from the reasons mentioned by repost agent, since you are checking today's bills, note that, the bill can take a day or two before it shows the desired bill. This is because of your timezone and billing/cost explorer timezones' differences. Most likely, cost explorer uses UTC, so, your change might appear a bit later.