Rain DNS Issues

Started again about 10 minutes ago.

Timestamp: 01/05/2018 08h44 (GMT+2):

Code: 
C:\Windows\system32>tracert www.cracked.com

Tracing route to a1776.g1.akamai.net [41.73.43.138]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  homerouter.cpe [192.168.8.1]
  2     *        *        *     Request timed out.
  3    42 ms    39 ms    49 ms  41.73.34.193
  4    29 ms    22 ms    19 ms  41.73.34.205
  5    50 ms    23 ms    20 ms  41.73.34.205
  6     *        *        *     Request timed out.
  7    38 ms    22 ms    19 ms  10.1.29.13
  8    31 ms    19 ms    19 ms  41.73.42.129
  9    51 ms    20 ms    17 ms  41.216.199.4
 10    29 ms    21 ms    18 ms  bnkcrs01-vl677.neology.io [41.216.193.66]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *     ^C


This one loads only partially as per posts above:

Timestamp: 01/05/2018 08h48 (GMT+2):

Code: 
C:\Windows\system32>tracert store.steampowered.com

Tracing route to store.steampowered.com [2.21.103.71]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  homerouter.cpe [192.168.8.1]
  2     *        *        *     Request timed out.
  3    36 ms    29 ms    33 ms  41.73.34.193
  4    31 ms    20 ms    20 ms  41.73.34.205
  5     *        *        *     Request timed out.
  6    32 ms    19 ms    19 ms  10.1.29.13
  7    29 ms    23 ms    19 ms  akamai.ixp.joburg [196.46.25.212]
  8    47 ms    20 ms    25 ms  2.21.103.71

Trace complete.
 
Iblis said:
Started again about 10 minutes ago.

Timestamp: 01/05/2018 08h44 (GMT+2):

Code: 
C:\Windows\system32>tracert www.cracked.com

Tracing route to a1776.g1.akamai.net [41.73.43.138]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  homerouter.cpe [192.168.8.1]
  2     *        *        *     Request timed out.
  3    42 ms    39 ms    49 ms  41.73.34.193
  4    29 ms    22 ms    19 ms  41.73.34.205
  5    50 ms    23 ms    20 ms  41.73.34.205
  6     *        *        *     Request timed out.
  7    38 ms    22 ms    19 ms  10.1.29.13
  8    31 ms    19 ms    19 ms  41.73.42.129
  9    51 ms    20 ms    17 ms  41.216.199.4
 10    29 ms    21 ms    18 ms  bnkcrs01-vl677.neology.io [41.216.193.66]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *     ^C


This one loads only partially as per posts above:

Timestamp: 01/05/2018 08h48 (GMT+2):

Code: 
C:\Windows\system32>tracert store.steampowered.com

Tracing route to store.steampowered.com [2.21.103.71]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  homerouter.cpe [192.168.8.1]
  2     *        *        *     Request timed out.
  3    36 ms    29 ms    33 ms  41.73.34.193
  4    31 ms    20 ms    20 ms  41.73.34.205
  5     *        *        *     Request timed out.
  6    32 ms    19 ms    19 ms  10.1.29.13
  7    29 ms    23 ms    19 ms  akamai.ixp.joburg [196.46.25.212]
  8    47 ms    20 ms    25 ms  2.21.103.71

Trace complete.
Click to expand...

That doesn't look great. We're not getting this in general at the moment.

Can you drop me a PM if you're still seeing this? :(
 
I am seeing it tonight.. its been off and on the past 2 weeks, one day working, one not... Quite frankly its getting ridiculous now.
Tonight (right now) Microsoft sites are once again useless to use.. See screen shot attached - and that's after waiting 7 minutes for page to load!

And here's the problem, a traceroute is currently going to an Akamai server in London! Something is totally screwed with the way the entire Akamai routing is set up....

$ traceroute account.microsoft.com
traceroute to e9412.b.akamaiedge.net (2.22.68.19), 64 hops max, 52 byte packets
1 homerouter.cpe (192.168.200.1) 1.159 ms 0.760 ms 0.606 ms
2 * * *
3 41.73.34.197 (41.73.34.197) 52.068 ms 50.157 ms 40.469 ms
4 41.73.34.201 (41.73.34.201) 72.051 ms 40.400 ms 48.905 ms
5 41.73.34.205 (41.73.34.205) 55.978 ms 37.516 ms 46.927 ms
6 * * *
7 10.1.29.13 (10.1.29.13) 42.885 ms 35.713 ms 48.934 ms
8 196.250.232.25 (196.250.232.25) 35.011 ms 34.577 ms 41.105 ms
9 154.66.247.179 (154.66.247.179) 208.847 ms 220.328 ms 219.904 ms
10 154.66.247.166 (154.66.247.166) 211.694 ms
xe-4-0-1.edge3.london15.level3.net (212.187.195.21) 207.159 ms
154.66.247.166 (154.66.247.166) 199.597 ms
11 xe-4-0-1.edge3.london15.level3.net (212.187.195.21) 199.287 ms * *
12 * * *
13 * * *
14 gtt-level3-100g.london15.level3.net (4.68.111.26) 213.309 ms 195.611 ms
et-5-3-0.cr5-lon2.ip4.gtt.net (89.149.182.9) 204.979 ms
15 2.22.68.19 (2.22.68.19) 213.427 ms
et-5-3-0.cr5-lon2.ip4.gtt.net (89.149.182.9) 204.576 ms
2.22.68.19 (2.22.68.19) 226.342 ms
 

Attachments

  • Screen Shot 2018-05-03 at 6.45.45 PM.jpg
    Screen Shot 2018-05-03 at 6.45.45 PM.jpg
    41.2 KB · Views: 79
racer said:
I am seeing it tonight.. its been off and on the past 2 weeks, one day working, one not... Quite frankly its getting ridiculous now.
Tonight (right now) Microsoft sites are once again useless to use.. See screen shot attached - and that's after waiting 7 minutes for page to load!

And here's the problem, a traceroute is currently going to an Akamai server in London! Something is totally screwed with the way the entire Akamai routing is set up....

$ traceroute account.microsoft.com
traceroute to e9412.b.akamaiedge.net (2.22.68.19), 64 hops max, 52 byte packets
1 homerouter.cpe (192.168.200.1) 1.159 ms 0.760 ms 0.606 ms
2 * * *
3 41.73.34.197 (41.73.34.197) 52.068 ms 50.157 ms 40.469 ms
4 41.73.34.201 (41.73.34.201) 72.051 ms 40.400 ms 48.905 ms
5 41.73.34.205 (41.73.34.205) 55.978 ms 37.516 ms 46.927 ms
6 * * *
7 10.1.29.13 (10.1.29.13) 42.885 ms 35.713 ms 48.934 ms
8 196.250.232.25 (196.250.232.25) 35.011 ms 34.577 ms 41.105 ms
9 154.66.247.179 (154.66.247.179) 208.847 ms 220.328 ms 219.904 ms
10 154.66.247.166 (154.66.247.166) 211.694 ms
xe-4-0-1.edge3.london15.level3.net (212.187.195.21) 207.159 ms
154.66.247.166 (154.66.247.166) 199.597 ms
11 xe-4-0-1.edge3.london15.level3.net (212.187.195.21) 199.287 ms * *
12 * * *
13 * * *
14 gtt-level3-100g.london15.level3.net (4.68.111.26) 213.309 ms 195.611 ms
et-5-3-0.cr5-lon2.ip4.gtt.net (89.149.182.9) 204.979 ms
15 2.22.68.19 (2.22.68.19) 213.427 ms
et-5-3-0.cr5-lon2.ip4.gtt.net (89.149.182.9) 204.576 ms
2.22.68.19 (2.22.68.19) 226.342 ms
Click to expand...

Thanks for testing. :) I can tell that this has been super frustrating. I've passed this onto our network team to investigate with Rain and hopefully get it sorted out once and for all.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X