I never thought to ping my E-66, what a crazy idea

From my work behind iiNet
Here are my worthless results to the rest of ya
3 22 ms 21 ms 21 ms nexthop.wa.iinet.net.au [203.59.14.16]
4 22 ms 23 ms 22 ms gi2-3.per-qv1-bdr2.iinet.net.au [203.215.4.30]
5 80 ms 80 ms 80 ms te1-0-1.per-qv1-bdr1.iinet.net.au [203.215.20.130]
6 78 ms 79 ms 79 ms te0-0-0.syd-ult-core1.iinet.net.au [203.215.20.6]
7 79 ms 79 ms 79 ms as10143.sydney.pipenetworks.com [218.100.2.16]
8 * * * Request timed out.
9 79 ms 79 ms 79 ms 45.2.233.220.static.exetel.com.au [220.233.2.45]
10 * * * Request timed out.
11 164 ms 162 ms 165 ms ADSL2+ in Perth
Reply from ADSL2+ in Perth: bytes=32 time=163ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=334ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=164ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=161ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=162ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=162ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=163ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=167ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=164ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=161ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=202ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=162ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=165ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=162ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=166ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=163ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=175ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=164ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=164ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=161ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=165ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=166ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=166ms TTL=119
Reply from ADSL2+ in Perth: bytes=32 time=167ms TTL=119
Then to my HSPA
3 22 ms 22 ms 22 ms nexthop.wa.iinet.net.au [203.59.14.16]
4 22 ms 22 ms 22 ms gi2-3.per-qv1-bdr1.iinet.net.au [203.215.4.28]
5 79 ms 78 ms 81 ms te0-0-0.syd-ult-core1.iinet.net.au [203.215.20.6]
6 80 ms 79 ms 79 ms as10143.sydney.pipenetworks.com [218.100.2.16]
7 * * * Request timed out.
8 81 ms 80 ms 79 ms 45.2.233.220.static.exetel.com.au [220.233.2.45]
9 92 ms 92 ms 91 ms 2.2.96.58.static.exetel.com.au [58.96.2.2]
10 93 ms 91 ms 92 ms 67.2.96.58.static.exetel.com.au [58.96.2.67]
11 1333 ms * 1445 ms HSPA in Perth on E-66
I'm in West Perth when conducting these tests, the phone has a full battery and a full signal bar solid. When pinging it, sometimes it would consistently get 250ms, 320ms, or 450ms, and occasionally time out and then have 1200ms+ for one packet and back to the ‘normal.’ But the first ping is always way high. So it would seem that it's technically possible to get solid 250ms if there isn't any other congestion. But I'll double check that test tonight at 1am.
Reply from HSPA in Perth on E-66: bytes=32 time=1353ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=434ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=450ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=407ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=443ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=422ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=499ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=436ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=501ms TTL=60
Request timed out.
Reply from HSPA in Perth on E-66: bytes=32 time=1238ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=472ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=423ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=419ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=409ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=449ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=445ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=405ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=406ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=405ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=441ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=448ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=445ms TTL=60
Reply from HSPA in Perth on E-66: bytes=32 time=423ms TTL=60