<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic twitter.com routing to Russian ISP in Everything else</title>
    <link>https://community.plus.net/t5/Everything-else/twitter-com-routing-to-Russian-ISP/m-p/1864102#M28264</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Just noticed that, on my broadband, twitter.com is routing to&amp;nbsp;mts-internet.net (a Russian ISP) and then looping. The website is obviously not working. It works fine on my Plusnet mobile 4G though&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any idea what is going on? I have a theory based on routes leaking from Russia but who knows...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;$ traceroute twitter.com                                                             
traceroute: Warning: twitter.com has multiple addresses; using 104.244.42.1
traceroute to twitter.com (104.244.42.1), 64 hops max, 52 byte packets
 1  10.0.0.1 (10.0.0.1)  8.239 ms  7.860 ms  6.138 ms
 2  192.168.1.254 (192.168.1.254)  7.406 ms  6.825 ms  8.734 ms
 3  251.core.plus.net (195.166.130.251)  15.027 ms  15.682 ms  13.902 ms
 4  84.93.253.91 (84.93.253.91)  15.795 ms  16.394 ms  15.913 ms
 5  195.99.125.144 (195.99.125.144)  16.146 ms
    195.99.125.140 (195.99.125.140)  16.539 ms  16.818 ms
 6  peer2-et-0-0-4.slough.ukcore.bt.net (109.159.252.118)  30.128 ms
    peer7-et-7-0-4.telehouse.ukcore.bt.net (62.172.103.164)  41.003 ms
    peer7-et-3-1-1.telehouse.ukcore.bt.net (109.159.252.164)  16.596 ms
 7  * * *
 8  tct-cr02-ae2.192.ams.mts-internet.net (195.34.53.81)  25.888 ms
    anc-cr01-be5.204.ff.mts-internet.net (195.34.53.225)  32.262 ms
    tct-cr02-ae2.192.ams.mts-internet.net (195.34.53.81)  26.119 ms
 9  * anc-cr03-ae5.131.ff.mts-internet.net (212.188.42.18)  77.125 ms *
10  * a433-cr02-be2.77.msk.mts-internet.net (212.188.28.150)  75.181 ms  66.104 ms
11  * m9-cr03-ae11.77.msk.mts-internet.net (212.188.42.125)  72.175 ms
    a197-cr01-ae6.77.msk.mts-internet.net (212.188.2.190)  68.286 ms
12  a433-cr02-be11.77.msk.mts-internet.net (212.188.42.126)  66.155 ms
    m9-cr03-ae11.77.msk.mts-internet.net (212.188.42.125)  67.749 ms
...&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 28 Mar 2022 12:55:02 GMT</pubDate>
    <dc:creator>joshberry</dc:creator>
    <dc:date>2022-03-28T12:55:02Z</dc:date>
    <item>
      <title>twitter.com routing to Russian ISP</title>
      <link>https://community.plus.net/t5/Everything-else/twitter-com-routing-to-Russian-ISP/m-p/1864102#M28264</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Just noticed that, on my broadband, twitter.com is routing to&amp;nbsp;mts-internet.net (a Russian ISP) and then looping. The website is obviously not working. It works fine on my Plusnet mobile 4G though&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any idea what is going on? I have a theory based on routes leaking from Russia but who knows...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;$ traceroute twitter.com                                                             
traceroute: Warning: twitter.com has multiple addresses; using 104.244.42.1
traceroute to twitter.com (104.244.42.1), 64 hops max, 52 byte packets
 1  10.0.0.1 (10.0.0.1)  8.239 ms  7.860 ms  6.138 ms
 2  192.168.1.254 (192.168.1.254)  7.406 ms  6.825 ms  8.734 ms
 3  251.core.plus.net (195.166.130.251)  15.027 ms  15.682 ms  13.902 ms
 4  84.93.253.91 (84.93.253.91)  15.795 ms  16.394 ms  15.913 ms
 5  195.99.125.144 (195.99.125.144)  16.146 ms
    195.99.125.140 (195.99.125.140)  16.539 ms  16.818 ms
 6  peer2-et-0-0-4.slough.ukcore.bt.net (109.159.252.118)  30.128 ms
    peer7-et-7-0-4.telehouse.ukcore.bt.net (62.172.103.164)  41.003 ms
    peer7-et-3-1-1.telehouse.ukcore.bt.net (109.159.252.164)  16.596 ms
 7  * * *
 8  tct-cr02-ae2.192.ams.mts-internet.net (195.34.53.81)  25.888 ms
    anc-cr01-be5.204.ff.mts-internet.net (195.34.53.225)  32.262 ms
    tct-cr02-ae2.192.ams.mts-internet.net (195.34.53.81)  26.119 ms
 9  * anc-cr03-ae5.131.ff.mts-internet.net (212.188.42.18)  77.125 ms *
10  * a433-cr02-be2.77.msk.mts-internet.net (212.188.28.150)  75.181 ms  66.104 ms
11  * m9-cr03-ae11.77.msk.mts-internet.net (212.188.42.125)  72.175 ms
    a197-cr01-ae6.77.msk.mts-internet.net (212.188.2.190)  68.286 ms
12  a433-cr02-be11.77.msk.mts-internet.net (212.188.42.126)  66.155 ms
    m9-cr03-ae11.77.msk.mts-internet.net (212.188.42.125)  67.749 ms
...&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Mar 2022 12:55:02 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/twitter-com-routing-to-Russian-ISP/m-p/1864102#M28264</guid>
      <dc:creator>joshberry</dc:creator>
      <dc:date>2022-03-28T12:55:02Z</dc:date>
    </item>
    <item>
      <title>Re: twitter.com routing to Russian ISP</title>
      <link>https://community.plus.net/t5/Everything-else/twitter-com-routing-to-Russian-ISP/m-p/1864103#M28265</link>
      <description>&lt;P&gt;...and now it is working again. Someone obviously fixed their mistake &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@13ACAF1B4DB3038AD540E11CDD6AB984/images/emoticons/cheesy.gif" alt="Cheesy" title="Cheesy" /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Mar 2022 12:59:40 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/twitter-com-routing-to-Russian-ISP/m-p/1864103#M28265</guid>
      <dc:creator>joshberry</dc:creator>
      <dc:date>2022-03-28T12:59:40Z</dc:date>
    </item>
    <item>
      <title>Re: twitter.com routing to Russian ISP</title>
      <link>https://community.plus.net/t5/Everything-else/twitter-com-routing-to-Russian-ISP/m-p/1864141#M28266</link>
      <description>&lt;P&gt;&lt;A href="https://news.ycombinator.com/item?id=30829876" target="_blank" rel="noopener"&gt;Twitter Routing Issue in UK? | Hacker News (ycombinator.com)&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;... Something odd going on with network routing to Twitter in the UK right now. From a BT Broadband home connection, traffic seems to be flowing via an "mts-internet.net" addresses listed in Moscow. I've tried from a VPN and can access Twitter just fine. Downdectector shows a peak in reports of issues too - &lt;A href="https://downdetector.co.uk/status/twitter/" target="_blank" rel="noopener"&gt;https://downdetector.co.uk/status/twitter/&lt;/A&gt;.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;... Noticed in Slovenia &amp;amp; France too!&lt;/P&gt;</description>
      <pubDate>Mon, 28 Mar 2022 15:50:31 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/twitter-com-routing-to-Russian-ISP/m-p/1864141#M28266</guid>
      <dc:creator>seebee</dc:creator>
      <dc:date>2022-03-28T15:50:31Z</dc:date>
    </item>
    <item>
      <title>Re: twitter.com routing to Russian ISP</title>
      <link>https://community.plus.net/t5/Everything-else/twitter-com-routing-to-Russian-ISP/m-p/1864146#M28267</link>
      <description>&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 28 Mar 2022 16:10:00 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/twitter-com-routing-to-Russian-ISP/m-p/1864146#M28267</guid>
      <dc:creator>joshberry</dc:creator>
      <dc:date>2022-03-28T16:10:00Z</dc:date>
    </item>
    <item>
      <title>Re: twitter.com routing to Russian ISP</title>
      <link>https://community.plus.net/t5/Everything-else/twitter-com-routing-to-Russian-ISP/m-p/1864159#M28268</link>
      <description>&lt;P&gt;Strange happenings in Soviet cybersphere ... now why am I suspicious? After&amp;nbsp;&lt;A href="https://community.plus.net/t5/General-Chat/I-don-t-trust-Kaspersky-any-more/m-p/1864156#M294991" target="_self"&gt;this&lt;/A&gt;&amp;nbsp;...&lt;/P&gt;</description>
      <pubDate>Mon, 28 Mar 2022 17:21:06 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/twitter-com-routing-to-Russian-ISP/m-p/1864159#M28268</guid>
      <dc:creator>Longliner</dc:creator>
      <dc:date>2022-03-28T17:21:06Z</dc:date>
    </item>
    <item>
      <title>Re: twitter.com routing to Russian ISP</title>
      <link>https://community.plus.net/t5/Everything-else/twitter-com-routing-to-Russian-ISP/m-p/1864276#M28269</link>
      <description>&lt;P&gt;This article:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://arstechnica.com/information-technology/2022/03/absence-of-malice-russian-isps-hijacking-of-twitter-ips-appears-to-be-a-goof/" target="_blank"&gt;https://arstechnica.com/information-technology/2022/03/absence-of-malice-russian-isps-hijacking-of-twitter-ips-appears-to-be-a-goof/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;indicates that it was a hamfisted attempt to block twitter inside Russia.&lt;/P&gt;
&lt;P&gt;However, the article also states that most ISP's prevented their twitter traffic from being mis-directed to Russia.&lt;/P&gt;
&lt;P&gt;If the article is correct, BT group could and should improve the integrity of their BGP tables to mitigate against future mis-routings deliberate or otherwise.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Mar 2022 14:32:48 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/twitter-com-routing-to-Russian-ISP/m-p/1864276#M28269</guid>
      <dc:creator>RichardB</dc:creator>
      <dc:date>2022-03-29T14:32:48Z</dc:date>
    </item>
  </channel>
</rss>

