Twitter, Cloudflare DNS, other routing issues?

[Zuccster]

Anyone else seeing a routing blackhole like this:

$ tracepath twitter.com
 1?: [LOCALHOST]                      pmtu 1500
 1:  RT-AC86U-60B0.local                                   6.848ms 
 1:  RT-AC86U-60B0.local                                   2.058ms 
 2:  RT-AC86U-60B0.local                                   2.252ms pmtu 1492
 2:  no reply
 3:  63.130.127.213                                        8.214ms asymm  4 
 4:  10.200.18.45                                         12.856ms 
 5:  63.130.104.198                                       11.914ms asymm  6 
 6:  63.130.127.213                                       10.504ms asymm  4 
 7:  10.200.18.45                                         10.930ms asymm  4 
 8:  63.130.104.198                                       11.497ms asymm  6 
 9:  63.130.127.213                                       12.669ms asymm  4 
10:  10.200.18.45                                         12.699ms asymm  4 
11:  63.130.104.198                                       15.672ms asymm  6 
12:  63.130.127.213                                       14.249ms asymm  4 
13:  10.200.18.45                                         14.565ms asymm  4 
14:  63.130.104.198                                       15.385ms asymm  6 
15:  63.130.127.213                                       16.622ms asymm  4 
16:  10.200.18.45                                         14.558ms asymm  4 
17:  63.130.104.198                                       17.474ms asymm  6 
18:  63.130.127.213                                       18.652ms asymm  4 
19:  10.200.18.45                                         17.761ms asymm  4 
20:  63.130.104.198                                       18.485ms asymm  6 
21:  63.130.127.213                                       17.823ms asymm  4 
22:  10.200.18.45                                         19.614ms asymm  4 
23:  63.130.104.198                                       20.963ms asymm  6 
24:  63.130.127.213                                       21.040ms asymm  4 
25:  10.200.18.45                                         20.610ms asymm  4 
26:  63.130.104.198                                       22.114ms asymm  6 
27:  63.130.127.213                                       21.395ms asymm  4 
28:  10.200.18.45                                         22.728ms asymm  4 
29:  63.130.104.198                                       23.665ms asymm  6 
30:  63.130.127.213                                       25.953ms asymm  4 
     Too many hops: pmtu 1492
     Resume: pmtu 1492

[tasitc]

When I last looked 1.0.0.1 (also cloudflare DNS) was still routing successfully (I'd forgotten so set it up which is why I noticed this routing loop)

@zuccster would you mind changing the topic of this thread to something like "Routing issue (Twitter, cloudflare DNS and probably others)" so others with issues find it?

[jibilah]

 I too am having issues from late evening of 18th June 2020 with using 1.1.1.1 as DNS.

Using 1.0.0.1 works fine. Tracert of both:

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  vodafone.broadband [192.168.1.1]
  2     4 ms     4 ms     4 ms  84.65.64.1
  3    19 ms    22 ms    22 ms  63.130.127.213
  4     6 ms     6 ms     6 ms  10.200.18.45
  5     6 ms     6 ms     5 ms  63.130.104.198
  6     7 ms     7 ms     7 ms  63.130.127.213
  7     8 ms     7 ms     7 ms  10.200.18.45
  8    12 ms    12 ms    13 ms  63.130.104.198
  9     8 ms     9 ms     9 ms  63.130.127.213
 10     9 ms     9 ms     9 ms  10.200.18.45
 11     9 ms     9 ms     8 ms  63.130.104.198
 12    10 ms    10 ms    10 ms  63.130.127.213
 13    10 ms    11 ms    10 ms  10.200.18.45
 14    10 ms    10 ms    10 ms  63.130.104.198
 15    20 ms    19 ms    20 ms  63.130.127.213
 16    11 ms    12 ms    11 ms  10.200.18.45
 17    11 ms    12 ms    11 ms  63.130.104.198
 18    13 ms    13 ms    13 ms  63.130.127.213
 19    14 ms    14 ms    14 ms  10.200.18.45
 20    14 ms    13 ms    13 ms  63.130.104.198
 21    16 ms    15 ms    15 ms  63.130.127.213
 22    15 ms    15 ms    15 ms  10.200.18.45
 23    15 ms    15 ms    15 ms  63.130.104.198
 24    17 ms    16 ms    16 ms  63.130.127.213
 25    16 ms    17 ms    17 ms  10.200.18.45
 26    20 ms    32 ms    30 ms  63.130.104.198
 27    18 ms    19 ms    18 ms  63.130.127.213
 28    18 ms    18 ms    18 ms  10.200.18.45
 29    33 ms    30 ms    21 ms  63.130.104.198
 30    19 ms    19 ms    19 ms  63.130.127.213

Trace complete

Tracing route to one.one.one.one [1.0.0.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  vodafone.broadband [192.168.1.1]
  2     5 ms     7 ms     3 ms  84.65.64.1
  3     4 ms     4 ms     4 ms  63.130.104.198
  4    19 ms    18 ms    18 ms  linx-lon1.as13335.net [195.66.225.179]
  5     8 ms     3 ms     4 ms  one.one.one.one [1.0.0.1]

Trace complete.

Can clearly see there's an issue here

[Zuccster]

1.1.1.1 is now working for me.

www.twitter.com (104.244.42.65 / 102.244.42.1) is sill going around in cricles.

[jibilah]

Likewise, a tracert of 1.1.1.1 successfully completes now:

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  vodafone.broadband [192.168.1.1]
  2     4 ms     4 ms     4 ms  84.65.64.1
  3     4 ms     4 ms     4 ms  63.130.104.198
  4     5 ms     5 ms     5 ms  linx-lon1.as13335.net [195.66.225.179]
  5     4 ms     4 ms     4 ms  one.one.one.one [1.1.1.1]

Trace complete.

But as you say, 104.244.42.65  keeps going round in circles, however I get the following for 102.244.42.1:

Tracing route to 102.244.42.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  vodafone.broadband [192.168.1.1]
  2     4 ms    13 ms    10 ms  84.65.64.1
  3    10 ms     8 ms     5 ms  63.130.104.198
  4     4 ms     4 ms     4 ms  ae11-100-xcr1.hex.cw.net [195.89.96.1]
  5    13 ms    13 ms    10 ms  ae17-xcr1.ltw.cw.net [195.2.28.150]
  6     5 ms     5 ms     5 ms  ae5-xcr1.slo.cw.net [195.2.24.33]
  7     5 ms     *       21 ms  94.142.107.82
  8    77 ms    77 ms    79 ms  213.140.43.149
  9   110 ms   110 ms   112 ms  5.53.6.202
 10   181 ms   186 ms   183 ms  213.140.39.175
 11   184 ms   184 ms   184 ms  154.72.188.97
 12   195 ms   185 ms   185 ms  154.72.188.10
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.

[SteamedHams]

Anyone got any further updates on this? been over a day with this issue for me

[Zuccster]

Tried to call back just now.  The issue number they texted me earlier wasn't recognised, so I was sent back to the queue for 1st line support again.  Estimated wait time 60-120mins.

I think others need to log the issue too.  Don't be fobbed off with the flimflam about needing to use their router, or leaving it for 24-48hrs.  It's a packet routing issue in their network.  Point the 2nd line people to this thread.

[joosters]

1.1.1.1 and www.twitter.com are still lost in routing loops for me.

Oddly enough, mobile.twitter.com is reachable though!

I'd like to raise a support issue too, but is there any other way than phoning them up? Do vodafone have a support email address?

[Zuccster]

No email address that I can find.  There's text chat, but it seem to be limited to level 1, escalation has to be via phone.

[joosters]

Sorry, I haven't got the time to spare on trying to get through their first line support, I admire your persistence though - how many times have they asked you to reboot your router?

[SteamedHams]

I also haven't got time to call, the live chat was not helpful and as suggested they can't escalate technical issues from there. Such a bizarre issue, annoyingly although mobile.twitter.com works, it won't redirect twitter.com visits to it on a mobile due to not loading in the first place.