SQL Elastic Pool Stuck on Scaling for 22 Hours

For performance testing I've scaled my SQL Elastic Pool from:

General Purpose - 18 vCores - 2TB Storage

to

Business Critical - 128 vCores - 3TB Storage

The main database in the pool has between 1TB to 1.5TB of data in, the rest have under 100GB and the process has been going on for 22 hours 54 minutes 56 seconds now.

Is there a way to check:

1. Is this expected for the size of data?
2. Is the scaling process still healthy and running?
3. How much we're being charged during this.

Thanks.