Welcome to Catch Up

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

CU+ http 504 error

Red Carpet

Re: CU+ http 504 error


@andrewgerm wrote:

For what it's worth, I just tried a tracert on: explora.dstvcdn.com again, and got 143.204.65.24.

If I flush my PC DNS, I then get 143.204.65.110, repeating, then hops between the two above.


Well done! You have highlighted another almost textbook case of poor configurations of how to handle overflow conditions. 

But in the process, we now have a solution to offer those experiencing this error by suggesting that they flush their local device DNS, in the hopes that then the vicious loop will be broken.

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
Anime

Re: CU+ http 504 error


@andrewgerm wrote:

For what it's worth, I just tried a tracert on: explora.dstvcdn.com again, and got 143.204.65.24.

If I flush my PC DNS, I then get 143.204.65.110, repeating, then hops between the two above.


You don't need to flush your DNS, Cloudfront will update DNS records dynamically in order to loadbalance their servers. If you just do multiple traceroutes, you'll find that some resolve to different IPs.

Re: CU+ http 504 error

For what it's worth, I just tried a tracert on: explora.dstvcdn.com again, and got 143.204.65.24.

If I flush my PC DNS, I then get 143.204.65.110, repeating, then hops between the two above.

BoxOffice

Re: CU+ http 504 error


@GeoffD wrote:

In fact it focusses the attention firmly on MCs internal setups and poor configurations.

 


This is what they don't seem to (or don't want to) understand. We're not sitting on dial-up modems any more.... 

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
Red Carpet

Re: CU+ http 504 error

Okay, those of you on fibre connections are the ONLY ones who can expect to get below about 20 ms. You are the lucky ones. The rest of us will not get those figures.

 

It still does not explain away the poor streaming performance. In fact it focusses the attention firmly on MCs internal setups and poor configurations.

There are more of these crazy routings ending up overseas instead of on the nearest edge CF routers.

What is pathetic is that someone like me, sitting at the end of a 2 Mbps ADSL line, can spent 60 minutes and with a few tests, can highlight and find all sorts of issues! MC on the other and, at the core, fiddles around for weeks and can't find and fix the problems.

Is

I will continue to list routers that are not configured properly if I find them. And then I can't even use the services!

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
Highlighted
BoxOffice

Re: CU+ http 504 error

Just a note.. when I still had ADSL and could test multiple ISPs,  explora.dstvcdn.com resolved differently between Mweb and AH. Some changes were made middle of last year in the handling of traffic from AH and there was a huge improvement

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


@GeoffD wrote:

2ms is impossible on any network in SA so that reading you got is just plain wrong.

 

 

Really?  I have 2 - 5 ms access to many Joburg servers, 25 - 30ms to those in Cape Town. It's the miracle of fibre and server co-location.

 

 

tracert explora.dstvcdn.com

Tracing route to d93iqhdba7sql.cloudfront.net [143.204.19.52]
over a maximum of 30 hops:

  1    18 ms    <1 ms    <1 ms  192.168.1.1
  2    11 ms     2 ms     2 ms  dsl-197-245-196-1.voxdsl.co.za [197.245.196.1]
  3     1 ms     1 ms     1 ms  41.193.14.49
  4     4 ms     1 ms     2 ms  41.193.14.182
  5     2 ms     1 ms     3 ms  196-60-9-105.ixp.joburg [196.60.9.105]
  6     2 ms     3 ms     5 ms  52.93.56.8
  7     2 ms     2 ms     2 ms  52.93.56.21
  8     1 ms     1 ms     2 ms  52.93.56.253
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     2 ms     1 ms     1 ms  server-143-204-19-52.jnb50.r.cloudfront.net [143.204.19.52]

Trace complete.
ping explora.dstvcdn.com -n 10

Pinging d93iqhdba7sql.cloudfront.net [143.204.19.52] with 32 bytes of data:
Reply from 143.204.19.52: bytes=32 time=9ms TTL=245
Reply from 143.204.19.52: bytes=32 time=2ms TTL=245
Reply from 143.204.19.52: bytes=32 time=2ms TTL=245
Reply from 143.204.19.52: bytes=32 time=4ms TTL=245
Reply from 143.204.19.52: bytes=32 time=10ms TTL=245
Reply from 143.204.19.52: bytes=32 time=2ms TTL=245
Reply from 143.204.19.52: bytes=32 time=2ms TTL=245
Reply from 143.204.19.52: bytes=32 time=1ms TTL=245
Reply from 143.204.19.52: bytes=32 time=3ms TTL=245
Reply from 143.204.19.52: bytes=32 time=2ms TTL=245

Ping statistics for 143.204.19.52:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 10ms, Average = 3ms

These are Amazon cloud server IPs that are physically located in SA. In theory all the MC content should be duplicated across many of these CF cdn servers to service multiple POPs. But it seems that there is some misconfiguration.

 

Edit: Here is a ping for the 213 IP (a bit more jitter):

ping explora.dstvcdn.com -n 10

Pinging d93iqhdba7sql.cloudfront.net [143.204.19.213] with 32 bytes of data:
Reply from 143.204.19.213: bytes=32 time=3ms TTL=247
Reply from 143.204.19.213: bytes=32 time=2ms TTL=247
Reply from 143.204.19.213: bytes=32 time=2ms TTL=247
Reply from 143.204.19.213: bytes=32 time=1ms TTL=247
Reply from 143.204.19.213: bytes=32 time=1ms TTL=247
Reply from 143.204.19.213: bytes=32 time=2ms TTL=247
Reply from 143.204.19.213: bytes=32 time=16ms TTL=247
Reply from 143.204.19.213: bytes=32 time=36ms TTL=247
Reply from 143.204.19.213: bytes=32 time=2ms TTL=247
Reply from 143.204.19.213: bytes=32 time=2ms TTL=247

Ping statistics for 143.204.19.213:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 36ms, Average = 6ms

And a tracert to that same IP

tracert explora.dstvcdn.com

Tracing route to d93iqhdba7sql.cloudfront.net [143.204.19.213]
over a maximum of 30 hops:

  1     2 ms     4 ms     9 ms  192.168.1.1
  2     2 ms     4 ms     3 ms  dsl-197-245-196-1.voxdsl.co.za [197.245.196.1]
  3    19 ms     2 ms    17 ms  41.193.14.49
  4     4 ms     1 ms     3 ms  41.193.14.182
  5     1 ms     2 ms     2 ms  196-60-9-105.ixp.joburg [196.60.9.105]
  6     3 ms     3 ms     2 ms  52.93.56.24
  7     2 ms     2 ms     2 ms  52.93.56.33
  8     2 ms     1 ms     2 ms  52.93.56.249
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     3 ms     1 ms     7 ms  server-143-204-19-213.jnb50.r.cloudfront.net [143.204.19.213]

Trace complete.

 edit2 - I haven't seen that IP you mentioned  anywhere in the thread (143.204.165.142). I have seen 143.204.65.142, though, which is the Cape Town CF server 

Red Carpet

Re: CU+ http 504 error

Legitimate CF Edge IP addresses:

So far, I have found the following legitimate addresses:

JNB: 143.204.19.149 ; 143.204.19.231

CPT: 143.204.65.110 ; 143.204.65.142

 

The wrong address found so far is:

CPT: 143.204.165.142

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
Red Carpet

Re: CU+ http 504 error

No not a mistake. MC customers should  default to the nearest to them local Edge connection, BUT there have been quite a few that ended up being pushed to the address I used, hence why I showed the tracert and pings for that edge connection which would definitely timeout. It shows that the cdn configs are not correct if it happens .......

 

Here is the full list of CF IP ranges:

{"CLOUDFRONT_GLOBAL_IP_LIST": ["52.124.128.0/17", "54.230.0.0/16", "54.239.128.0/18", "99.84.0.0/16", "205.251.192.0/19", "54.239.192.0/19", "70.132.0.0/18", "13.32.0.0/15", "13.35.0.0/16", "204.246.172.0/23", "204.246.164.0/22", "204.246.168.0/22", "71.152.0.0/17", "216.137.32.0/19", "205.251.249.0/24", "99.86.0.0/16", "52.46.0.0/18", "52.84.0.0/15", "64.252.64.0/18", "204.246.174.0/23", "205.251.254.0/24", "143.204.0.0/16", "205.251.252.0/23", "204.246.176.0/20", "13.249.0.0/16", "54.240.128.0/18", "205.251.250.0/23", "52.222.128.0/17", "54.182.0.0/16", "54.192.0.0/16"], "CLOUDFRONT_REGIONAL_EDGE_IP_LIST": ["13.124.199.0/24", "34.226.14.0/24", "52.15.127.128/26", "35.158.136.0/24", "52.57.254.0/24", "18.216.170.128/25", "13.54.63.128/26", "13.59.250.0/26", "35.167.191.128/26", "52.47.139.0/24", "52.199.127.192/26", "52.212.248.0/26", "52.66.194.128/26", "13.113.203.0/24", "34.195.252.0/24", "35.162.63.192/26", "52.56.127.0/25", "13.228.69.0/24", "34.216.51.0/25", "54.233.255.128/26", "52.52.191.128/26", "52.78.247.128/26", "52.220.191.0/26", "34.232.163.208/29"]}
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
BoxOffice

Re: CU+ http 504 error

@Geoff   -  Your IP

tracert 143.204.165.142

is incorrect, should be 143.204.65.142

 

Btw, here is my stats to the 2ms server Smiley Happy  So ... getting close ..

Tracing route to server-143-204-19-231.jnb50.r.cloudfront.net [143.204.19.231]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dlinkrouter [192.168.0.1]
2 * * * Request timed out.
3 5 ms 4 ms 4 ms jhb-up1.ip.adsl.co.za [169.1.5.5]
4 5 ms 4 ms 4 ms 169-1-5-202.ip.afrihost.co.za [169.1.5.202]
5 13 ms 20 ms 4 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 4 ms 3 ms 4 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
7 4 ms 5 ms 4 ms 196-60-9-105.ixp.joburg [196.60.9.105]
8 4 ms 4 ms 4 ms 52.93.56.72
9 5 ms 4 ms 4 ms 52.93.56.83
10 4 ms 4 ms 4 ms 52.93.56.251
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 4 ms 4 ms 4 ms server-143-204-19-231.jnb50.r.cloudfront.net [143.204.19.231]

Trace complete.

 

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