On 26 October, our Bigpond ADSL service was activated.
My partner spoke to Bigpond and queried the availability of this service (given the information provided by Telstra previously that they would be unlikely to provide Bigpond ADSL to us because of the "issues on the RIM").
He was assured that there were no faults on any infrastructure. Really? Really Telstra?
How very interesting.
So here we are, a valued Telstra customer and the proud owners of two ADSL Services - one with Internode, one with Bigpond.
It should be noted that we have the links running on different equipment, totally independent of each other. Two very distinct and separate services.
So if the Telstra Wholesale reports are showing no spare ports on the DA we're connected to, where are we routing? Maybe we're on a different RIM? Could it be that by some magic or intervention by a supreme higher being, we have been transposed off the RIM completely? We should be so lucky.
It didn't take too long before we got to test both services. The usual nightly congestion started and we monitored both links.
Well will you look at that. Latency is woeful on both services. only with the Telstra service, we get 12% packet loss as well. Ace.
Request timed out.
Reply from 61.9.133.193: bytes=32 time=345ms TTL=123
Reply from 61.9.133.193: bytes=32 time=424ms TTL=123
Reply from 61.9.133.193: bytes=32 time=454ms TTL=123
Reply from 61.9.133.193: bytes=32 time=644ms TTL=123
Reply from 61.9.133.193: bytes=32 time=537ms TTL=123
Reply from 61.9.133.193: bytes=32 time=566ms TTL=123
Reply from 61.9.133.193: bytes=32 time=625ms TTL=123
Reply from 61.9.133.193: bytes=32 time=363ms TTL=123
Reply from 61.9.133.193: bytes=32 time=281ms TTL=123
Reply from 61.9.133.193: bytes=32 time=223ms TTL=123
Reply from 61.9.133.193: bytes=32 time=205ms TTL=123
Reply from 61.9.133.193: bytes=32 time=273ms TTL=123
Reply from 61.9.133.193: bytes=32 time=341ms TTL=123
Reply from 61.9.133.193: bytes=32 time=301ms TTL=123
Reply from 61.9.133.193: bytes=32 time=399ms TTL=123
Reply from 61.9.133.193: bytes=32 time=305ms TTL=123
Ping statistics for 61.9.133.193:
Packets: Sent = 103, Received = 90, Lost = 13 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 644ms, Average = 350ms
Congestion? Check.
Direct Relationship? Check.
Posts
More, more!
ReplyDeleteI had similar problems with a cable ISP back in the late 90's. I eventually managed to get a dedicated technical contact who I could work with. Then I set up a script that would run an extended ping once an hour, and email the tech if there was packetloss. There always was, 24/7, to the tune of 12-15%. The constant bombardmand of proof of problem inspired him to try to fix it, plus they couldn't actually charge me for using a clearly broken service; with the written documentation I had, they would never have been able to claim they were providing proper service.
ReplyDeleteThey tried a few times to play the 'You should just go elsewhere' card, but I stuck with it. Eventually, I am pretty sure they rewired from the headend to my house with brand new cable and junctions, improving service for both cable and internet for my entire neighborhood, just to shut me up. ;)