Welcome to Catch Up

cancel
Showing results for 
Search instead for 
Did you mean: 
Need help?

CU+ http 504 error

Showmaxed

Re: CU+ http 504 error


@andrewgerm wrote:

...but I think there was quite an issue on the SA Internet...


I don't recall trouble on Fri. night here, but we had a lot of all round problems later yesterday. (MWEB ADSL)

Re: CU+ http 504 error

I did a few tracerts Friday (nothing since) and the results were terrible, over 250ms on most hops. Swapped my DNS from 1.1.1.1 to 8.8.8.8, and eventually to MWebs (my ISP). No luck, but I think there was quite an issue on the SA Internet, as gaming, and many other issues had very high latency, even links between JHB and CPT.

 

That aside, I had really decent speeds this weekend with the CU+ app on Android.

 

Downloads to the deocder haven't been good though. Friday issues aside. How is the MC content delivered / stored? Do they have data centres (plural) across SA, such as CPT and JHB? If I can stream YouTube so well anywhere, then they can't blame external issues, and need to look at their own infrastructure (if they would at all listen).

Red Carpet

Re: CU+ http 504 error

What was happening 5 years ago was, that once the traffic was delivered to MC or its partners infrastructure, the traffic ended up tromboning between JHB and CT within their own setup,  It is that aspect that was removed, as well one of their links was upgraded in capacity. At some stage the powers that be reversed the removal.  There was a vast improvement when the tromboning was removed. And many of the issues returned.  Right now, you are correct an extra 20 ms within the network makes very little difference overall now.

So what these traces show is that the issues are still squarely withing MCs own environment and NOT in general, the decoder, the customer installations, the ISPs or the networks.

Octo LNB; 2 by 2x4 MS; 2 by ES 5-2; Dedicated PSU for LNB, ES's, MS's; HD PVR 4P x 2; Explora 1; DSD 660; FSM
Showmaxed

Re: CU+ http 504 error


@Optimist wrote:
Please can we have confirmation that these discussions and their revelations will be passed on to the correct most senior department management.

No answer from MC...

Showmaxed

Re: CU+ http 504 error

Ok. I don't remember more or know enough about this subject, but odd general CT routing of some sort was a major part of the concerns then so wouldn't be surprised if it still is involved somewhere.

Highlighted
Anime

Re: CU+ http 504 error

Nah, I don't think it is MC. That routing is LiquidTelecom. They've obviously prioritised a capetown internet exchange to connect to cloudfront.  It shouldn't make much difference to the user (less than 20 extra ms) for users in Joburg.

 



Could be the same as what Geoff analysed and advised on years ago.

Senior management took him seriously and had the CT detour removed - service improved a lot.

 


 

Showmaxed

Re: CU+ http 504 error


@arf9999 wrote:
Seems strange that your route goes via cape town to cloudfront.

Could be the same as what Geoff analysed and advised on years ago.

Senior management took him seriously and had the CT detour removed - service improved a lot.

Along came some cleva character and reversed that back into existence again, service went bad again. Never got further feedback, Geoff and others gave up.

 

Wouldn't be surprised if it's related to imagined security monitoring or controlling needs, or some market manipulation.

 

 

Please can we have confirmation that these discussions and their revelations will be passed on to the correct most senior department management.

Anime

Re: CU+ http 504 error

There's quite a jump in latency in those liquidtelecom hops.

 

Seems strange that your route goes via cape town to cloudfront.

BoxOffice

Re: CU+ http 504 error

Interesting how AfrihostOpenserve resolves differently from Vox

SLNB LMX501| Explora 2A (Primary 4,5,6) Explora 2A (Secondary 0,1,2) | Xtraview - decoders same room | 3 distributed HDMI endpoints via 2x4 Matrix
and Cat6 | 200/100 Fibre (OpenServe/Afrihost Premium UnCapped) | HD 5S in holiday mode
Anime

Re: CU+ http 504 error

Pinging d93iqhdba7sql.cloudfront.net [143.204.19.149] with 32 bytes of data:
Reply from 143.204.19.149: bytes=32 time=4ms TTL=245
Reply from 143.204.19.149: bytes=32 time=1ms TTL=245
Reply from 143.204.19.149: bytes=32 time=4ms TTL=245
Reply from 143.204.19.149: bytes=32 time=1ms TTL=245
Reply from 143.204.19.149: bytes=32 time=2ms TTL=245
Reply from 143.204.19.149: bytes=32 time=34ms TTL=245
Reply from 143.204.19.149: bytes=32 time=2ms TTL=245
Reply from 143.204.19.149: bytes=32 time=2ms TTL=245
Reply from 143.204.19.149: bytes=32 time=2ms TTL=245
Reply from 143.204.19.149: bytes=32 time=2ms TTL=245

Ping statistics for 143.204.19.149:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 34ms, Average = 5ms
Tracing route to d93iqhdba7sql.cloudfront.net [143.204.19.231]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     5 ms     8 ms     5 ms  dsl-197-245-196-1.voxdsl.co.za [197.245.196.1]
  3    14 ms     1 ms     1 ms  41.193.14.49
  4     3 ms     1 ms     1 ms  41.193.14.182
  5     2 ms     2 ms     1 ms  196-60-9-105.ixp.joburg [196.60.9.105]
  6     2 ms     2 ms     2 ms  52.93.56.72
  7     2 ms     2 ms     2 ms  52.93.56.87
  8     2 ms     2 ms     1 ms  52.93.56.255
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     1 ms     2 ms     2 ms  server-143-204-19-231.jnb50.r.cloudfront.net [143.204.19.231]

Trace complete.

It is not a network issue.  There are no latency issues, there are no dropped packets, the tracert is good. It is an issue in DStv's internal content delivery network. 

 

If one more call centre agent asks me to reboot the explora or reboot my router, I may be forced into violence.