Routing issue to Denver

I'm experiencing the same issues as tact and Moh. Seeing the responses to their complaints greatly prevents my decision to upgrading to a business plan.

Here are the original/optimal trace-routes towards denver IPs within hiperZ:

Tracing route to hosted-by.hiperz.com [84.17.63.106]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 10.31.192.1
2 5 ms 5 ms 5 ms GTD-DRUM-R2.bb.telus.com [154.11.15.194]
3 5 ms 6 ms 5 ms be-205-pe12.seattle.wa.ibone.comcast.net [173.167.57.213]
4 30 ms 30 ms 30 ms be-3412-pe12.910fifteenth.co.ibone.comcast.net [96.110.33.142]
5 33 ms 33 ms 33 ms 50.248.116.242
6 * * * Request timed out.
7 33 ms 33 ms 33 ms hosted-by.hiperz.com [84.17.63.106]

Tracing route to hosted-by.hiperz.com [84.17.63.96]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.31.192.1
2 * * 1 ms 173.182.212.84
3 * * * Request timed out.
4 * * * Request timed out.
5 32 ms 33 ms 33 ms 50.248.116.242
6 * * * Request timed out.
7 32 ms 33 ms 33 ms hosted-by.hiperz.com [84.17.63.96]

Today:

Tracing route to hosted-by.hiperz.com [84.17.63.96]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.31.192.1
2 1 ms <1 ms <1 ms 173.182.212.82
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 81 ms 80 ms 80 ms hosted-by.hiperz.com [84.17.63.96]

Tracing route to hosted-by.hiperz.com [84.17.63.106]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.31.192.1
2 <1 ms <1 ms <1 ms 173.182.212.82
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 81 ms 81 ms 81 ms hosted-by.hiperz.com [84.17.63.106]

Can a business plan help influence these routes or at least provide a direct line to solve routing issues?