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

[Zuccster]

Yay, it's sorted here too.

traceroute to www.twitter.com (104.244.42.65), 30 hops max, 38 byte packets
 1  *  *  *
 2  63.130.127.213 (63.130.127.213)  5.957 ms  5.879 ms  5.433 ms
 3  10.200.18.45 (10.200.18.45)  6.005 ms  6.141 ms  5.850 ms
 4  63.130.105.130 (63.130.105.130)  7.275 ms  7.394 ms  7.034 ms
 5  63.130.104.194 (63.130.104.194)  8.241 ms  7.968 ms  7.799 ms
 6  10.200.18.37 (10.200.18.37)  8.785 ms  8.465 ms  8.354 ms
 7  xe-1-1-0.cr1-lon1.twttr.com (195.66.225.142)  9.683 ms  9.748 ms  9.997 ms
 8  104.244.42.65 (104.244.42.65)  8.671 ms  8.972 ms  8.733 ms

[jibilah]

Yep likewise here!

[tasitc]

I assume we'll never get an RFO (reason for outage) from Vodafone?

This'll just slip into a working state with us none the wiser?

[WeeRed]

Fixed for me too. No official response from Vodafone UK support. So I'm very thankful to everyone here who helped. Thank you.

[Zuccster]

To my knowledge Vodafone never acknowledged there was a fault. 

I reported the issue Thurs eve via text chat, but they were unable to help.

I spoke to second line support on Fri AM who didn't really believe / understand the issue, but escalated it.  They told me 3rd line don't speak to customers directly.

The automated system never recognised the issue number I was given, and despite a couple of hours on hold yesterday (across two separate calls) I didn't manage to get back through to first line support.

I tweeted @VodafoneUK twice with details and pointed them here, but was not acknowledged.

I know from other threads that VF staff read these forums, so all it all the total radio-silence regarding this issue is a pretty poor show.   Are VF any worse than other ISPs?  Sadly, probably not.  At least everyone I spoke to was polite and tried to be helpful.

[fititome]

Sigh, only just seen this.  Identical issues to you guys.  The problem was resolved by this morning.  Support via messenger (where I posted all the logs and screenshots etc.) was never responded to. 

Curiously, throughout I was able to ping and tracert to mobile.twitter.com but not twitter.com.  Figure that one out. 

Even now the routes are different.  I guess one is routed through GCHQ. lol

[npetalas]

I get the same routing loop trying to resolve stackoverflow.com

Tracing route to stackoverflow.com [151.101.1.69]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  vodafone.connect [192.168.1.1]
  2    11 ms    11 ms    11 ms  host-212-158-250-37.dslgb.com [212.158.250.37]
  3     6 ms     7 ms     8 ms  63.130.104.194
  4    19 ms    18 ms    16 ms  10.200.18.37
  5    11 ms    11 ms    10 ms  63.130.105.130
  6    11 ms    15 ms    14 ms  63.130.104.194
  7    29 ms    25 ms    25 ms  10.200.18.37
  8    10 ms    17 ms    20 ms  63.130.105.130
  9    12 ms    13 ms    10 ms  63.130.104.194
 10    19 ms    19 ms    19 ms  10.200.18.37
 11    16 ms    16 ms    18 ms  63.130.105.130
...

[Velltho]

I am also experiencing routing issues. Traceroutes to affected sites included below:

Tracing route to imgur.com [151.101.60.193]
over a maximum of 30 hops:
1 3 ms <1 ms <1 ms vodafone.broadband [192.168.1.1]
2 6 ms 6 ms 6 ms host-212-158-250-36.dslgb.com [212.158.250.36]
3 8 ms 8 ms 8 ms 63.130.104.194
4 9 ms 9 ms 9 ms 10.200.18.37
5 8 ms 8 ms 9 ms 63.130.105.130
6 10 ms 9 ms 9 ms 63.130.104.194
7 11 ms 10 ms 10 ms 10.200.18.37
8 9 ms 9 ms 9 ms 63.130.105.130
-snip-
27 17 ms 17 ms 16 ms 63.130.104.194
28 21 ms 18 ms 16 ms 10.200.18.37
29 16 ms 16 ms 19 ms 63.130.105.130
30 19 ms 17 ms 17 ms 63.130.104.194

Trace complete.

Tracing route to stackoverflow.com [151.101.129.69]
over a maximum of 30 hops:

  1     3 ms    <1 ms    <1 ms  vodafone.broadband [192.168.1.1]
  2     7 ms     8 ms    17 ms  host-212-158-250-36.dslgb.com [212.158.250.36]
  3     9 ms     8 ms     8 ms  63.130.104.194
  4     8 ms     8 ms     9 ms  10.200.18.37
  5     8 ms    11 ms     8 ms  63.130.105.130
  6    11 ms    10 ms    10 ms  63.130.104.194
  7     9 ms     9 ms     9 ms  10.200.18.37
  8     9 ms    11 ms     9 ms  63.130.105.130
 -snip-
 27    17 ms    18 ms    16 ms  63.130.104.194
 28    17 ms    16 ms    16 ms  10.200.18.37
 29    16 ms    16 ms    16 ms  63.130.105.130
 30    17 ms    17 ms    17 ms  63.130.104.194

Trace complete.

[alan01252]

Another plus one from me here

[Zuccster]

OP here.  Although I'm not seeing the same issue as you this time, I'd like to share my experience of getting this resolved last time:

You'll need to call VF and persist until you talk to L2 support, who will relay info the L3.  L3 don't talk to humans. Forget chat, or this forum.  Don't expect to talk to anyone who understands networking at even the simplest level.

By all means start a new thread here and refer L2 to it.