Either the "MySQL Service" docker is broken or the way Railway is calculating "disk usage" is broken.

I have a database ~ 70MB in MySQL.
On an offline server I have the disk usage for it is ~130MB.

If I download the entire railway MySQL db as a backup it is a 130MB file.

Railway storage is > 4GB and growing daily.

I have tried running "Optimize tables" on the database and no real impact is seen.

With no real access to the MySQL docker there is not much more I can do to diagnose.

I am only a hobby user so am restricted to community support, and so far it has been to point the blame to MySQL (which I have demonstrated does not appear to be at fault)

I will soon hit the 5GB cap and will be none the wiser as to why.