Although RT was taken off-air on 3 March, it has still been available
online. However, today all I get is an 'Unable to connect' message (even
for the basic website).
https://www.rt.com and https://www.rt.com/on-air appear to be working,
I note that they want you to install a Firefox extension - I wouldn't
touch that with a bargepole.
Although RT was taken off-air on 3 March, it has still been available
online. However, today all I get is an 'Unable to connect' message (even
for the basic website). Does anyone know if it has been taken off
totally, or is this just an ISP decision? [Actually, although it does
give a fascinating insight into the present Russian perverted view of
the world, I'm surprised it has still been available for so long.]
On 12/05/2022 21:42, Ian Jackson wrote:
Although RT was taken off-air on 3 March, it has still been available
online. However, today all I get is an 'Unable to connect' message
(even for the basic website). Does anyone know if it has been taken
off totally, or is this just an ISP decision? [Actually, although it
does give a fascinating insight into the present Russian perverted
view of the world, I'm surprised it has still been available for so
long.]
I can't connect to rt.com [91.215.41.4] with Virgin Media or with
NordVPN (not even with their Indian server). All fail at twelve99.net in
(I think) USA. Don't ask me why.
Tracing route to 91.215.41.4 over a maximum of 30 hops
...
9 22 ms 29 ms 21 ms perr-wblk-1b-xe-200-0.network.virginmedia.net [62.254.1.218]
10 * * * Request timed out.
11 22 ms 21 ms 20 ms ldn-b3-link.ip.twelve99.net [213.248.84.25]
12 20 ms 19 ms 20 ms ldn-bb4-link.ip.twelve99.net [62.115.122.180]
13 34 ms 33 ms 32 ms hbg-bb4-link.ip.twelve99.net [62.115.122.160]
14 42 ms 43 ms 42 ms s-bb2-link.ip.twelve99.net [62.115.115.59]
15 52 ms 52 ms 52 ms sap-b4-link.ip.twelve99.net [62.115.115.247]
16 * * * Request timed out. ...
...
7 267 ms 267 ms 267 ms ldn-bb1-link.ip.twelve99.net [62.115.138.168]
8 278 ms 279 ms 278 ms hbg-bb3-link.ip.twelve99.net [80.91.249.11]
9 291 ms 291 ms 290 ms s-bb1-link.ip.twelve99.net [62.115.134.95]
10 304 ms 304 ms 305 ms sap-b4-link.ip.twelve99.net [62.115.143.31]
11 * * * Request timed out.
...
Tracing route to 91.215.41.4 over a maximum of 30 hops
I can't connect to rt.com [91.215.41.4] with Virgin Media or with NordVPN (not
even with their Indian server). All fail at twelve99.net in (I think) USA. Don't
ask me why.
I can't connect to rt.com [91.215.41.4] with Virgin Media or with NordVPN
(not even with their Indian server). All fail at twelve99.net in (I
think) USA. Don't ask me why.
From plusnet it doesn't pass through twelve99, but neither ping or
traceroute shows as reaching the destination, but https works.
Tracing route to rt.com [91.215.41.4]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.lan [192.168.1.1]
2 12 ms 11 ms 12 ms 195.166.130.249
3 12 ms 13 ms 12 ms gi2-23-442.ptn-gw02.plus.net
[84.93.253.75]
4 13 ms 18 ms 12 ms core1-BE1.colindale.ukcore.bt.net [195.99.125.132]
5 13 ms 13 ms 13 ms core5-hu0-7-0-15.faraday.ukcore.bt.net [195.99.127.36]
6 13 ms 12 ms 12 ms 166-49-209-132.gia.bt.net [166.49.209.132]
7 14 ms 15 ms 14 ms 212.119.4.140
8 14 ms 13 ms 14 ms ae-7.r20.londen12.uk.bb.gin.ntt.net [129.250.4.140]
9 * * * Request timed out.
10 86 ms 86 ms 85 ms ae-1.r00.nycmny13.us.bb.gin.ntt.net [129.250.2.174]
11 * * * Request timed out.
12 * * * Request timed out ... rinse ... repeat.
Intriguingly, my Plusnet connection (with a TPLink router, not a Plusnet one) resolves rt.com to 127.0.0.1 (local loopback) on both Windows and Linux (Raspbian).
That's for the router's DHCP allocating 192.168.1.1 / 208.67.222.222 (OpenDNS)
as primary and secondary DNS servers for use by clients, and the router's WAN connection set to 212.159.6.9 / 212.159.6.10 (Plusnet's DNS). I presume the combination of the two means that it tries 212.159.6.9 first, then 212.159.6.10
and finally 208.67.222.222. (*)
"Andy Burns" <usenet@andyburns.uk> wrote in message news:je6jgaF8f0eU1@mid.individual.net...
I can't connect to rt.com [91.215.41.4] with Virgin Media or with
NordVPN (not even with their Indian server). All fail at twelve99.net in >>> (I think) USA. Don't ask me why.
From plusnet it doesn't pass through twelve99, but neither ping or
traceroute shows as reaching the destination, but https works.
Tracing route to rt.com [91.215.41.4]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.lan [192.168.1.1]
2 12 ms 11 ms 12 ms 195.166.130.249
3 12 ms 13 ms 12 ms gi2-23-442.ptn-gw02.plus.net
[84.93.253.75]
4 13 ms 18 ms 12 ms core1-BE1.colindale.ukcore.bt.net
[195.99.125.132]
5 13 ms 13 ms 13 ms core5-hu0-7-0-15.faraday.ukcore.bt.net
[195.99.127.36]
6 13 ms 12 ms 12 ms 166-49-209-132.gia.bt.net
[166.49.209.132]
7 14 ms 15 ms 14 ms 212.119.4.140
8 14 ms 13 ms 14 ms ae-7.r20.londen12.uk.bb.gin.ntt.net
[129.250.4.140]
9 * * * Request timed out.
10 86 ms 86 ms 85 ms ae-1.r00.nycmny13.us.bb.gin.ntt.net
[129.250.2.174]
11 * * * Request timed out.
12 * * * Request timed out ... rinse ... repeat.
Intriguingly, my Plusnet connection (with a TPLink router, not a Plusnet
one) resolves rt.com to 127.0.0.1 (local loopback) on both Windows and
Linux (Raspbian).
That's for the router's DHCP allocating 192.168.1.1 / 208.67.222.222 (OpenDNS) as primary and secondary DNS servers for use by clients, and the router's WAN connection set to 212.159.6.9 / 212.159.6.10 (Plusnet's DNS).
I presume the combination of the two means that it tries 212.159.6.9
first, then 212.159.6.10 and finally 208.67.222.222. (*)
I wonder if some DNS servers have been "poisoned" so they will not resolve rt.com, and instead "resolve" it to localhost so it fails gracefully. If I set my Android phone to use Vodafone's mobile internet instead of
Plusnet's connection, I can resolve and ping the RT server.
you're not missing anything except Putin's propaganda.
I've just spotted: line "8" on your tracert refers to a server called >"londen12" - ie with an E not an O ;-)
"Andy Burns" <usenet@andyburns.uk> wrote in message news:je6jgaF8f0eU1@mid.individual.net...[Quoting broken, someone else wrote:]
I can't connect to rt.com [91.215.41.4] with Virgin Media or with
NordVPN (not even with their Indian server). All fail at twelve99.net
in (I think) USA. Don't ask me why.
From plusnet it doesn't pass through twelve99, but neither ping or
traceroute shows as reaching the destination, but https works.
Tracing route to rt.com [91.215.41.4]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.lan [192.168.1.1]
2 12 ms 11 ms 12 ms 195.166.130.249
3 12 ms 13 ms 12 ms gi2-23-442.ptn-gw02.plus.net
[84.93.253.75]
4 13 ms 18 ms 12 ms core1-BE1.colindale.ukcore.bt.net >> [195.99.125.132]
5 13 ms 13 ms 13 ms core5-hu0-7-0-15.faraday.ukcore.bt.net
[195.99.127.36]
6 13 ms 12 ms 12 ms 166-49-209-132.gia.bt.net
[166.49.209.132]
7 14 ms 15 ms 14 ms 212.119.4.140
8 14 ms 13 ms 14 ms ae-7.r20.londen12.uk.bb.gin.ntt.net
[129.250.4.140]
9 * * * Request timed out.
10 86 ms 86 ms 85 ms ae-1.r00.nycmny13.us.bb.gin.ntt.net
[129.250.2.174]
11 * * * Request timed out.
12 * * * Request timed out ... rinse ... repeat.
Intriguingly, my Plusnet connection (with a TPLink router, not a Plusnet
one) resolves rt.com to 127.0.0.1 (local loopback) on both Windows and
Linux (Raspbian).
That's for the router's DHCP allocating 192.168.1.1 / 208.67.222.222 (OpenDNS) as primary and secondary DNS servers for use by clients, and
the router's WAN connection set to 212.159.6.9 / 212.159.6.10 (Plusnet's DNS). I presume the combination of the two means that it tries
212.159.6.9 first, then 212.159.6.10 and finally 208.67.222.222. (*)
I wonder if some DNS servers have been "poisoned" so they will not
resolve rt.com, and instead "resolve" it to localhost so it fails
gracefully. If I set my Android phone to use Vodafone's mobile internet instead of Plusnet's connection, I can resolve and ping the RT server.
(*) The mixture of DNS servers was an attempt to work around an
intermittent problem where one Android phone on the network sometimes
(for about a week) fails to connect to one specific web site, although
all other devices manage it perfectly - so I wanted to be able to fall
back to an non-ISP DNS if there was an intermittent problem with the
ISP's ones. It didn't work! The fault remains, and is not cured by
rebooting phone or router, or by clearing the phone's DNS cache. It
fails almost 100% of the time for every attempt, then suddenly one day
works perfectly for a week or so, then it almost consistently fails
again. Since the phone is connected by wifi, it is difficult to gather
LAN traces with Wireshark because WS on a Windows/Linux PC (even if
connected by wifi) cannot see all the phone-router traffic. Running NetAnalyzer Pro on the phone shows that at times of failure, pings by
URL or IP work, but that a port scan finds all the web servers ports are closed or blocked. I can't decide whether it's a phone or ISP problem,
but it is significant that if I turn off the phone's wifi, forcing it to connect by Vodafone mobile internet, it always works... But if it was an
ISP problem (which is what it looks like) why would it only affect one device?
"Andy Burns" <usenet@andyburns.uk> wrote in message news:je6jgaF8f0eU1@mid.individual.net...
I can't connect to rt.com [91.215.41.4] with Virgin Media or with
NordVPN (not even with their Indian server). All fail at twelve99.net
in (I think) USA. Don't ask me why.
From plusnet it doesn't pass through twelve99, but neither ping or
traceroute shows as reaching the destination, but https works.
Tracing route to rt.com [91.215.41.4]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.lan [192.168.1.1]
2 12 ms 11 ms 12 ms 195.166.130.249
3 12 ms 13 ms 12 ms gi2-23-442.ptn-gw02.plus.net
[84.93.253.75]
4 13 ms 18 ms 12 ms core1-BE1.colindale.ukcore.bt.net >> [195.99.125.132]
5 13 ms 13 ms 13 ms core5-hu0-7-0-15.faraday.ukcore.bt.net
[195.99.127.36]
6 13 ms 12 ms 12 ms 166-49-209-132.gia.bt.net
[166.49.209.132]
7 14 ms 15 ms 14 ms 212.119.4.140
8 14 ms 13 ms 14 ms ae-7.r20.londen12.uk.bb.gin.ntt.net
[129.250.4.140]
9 * * * Request timed out.
10 86 ms 86 ms 85 ms ae-1.r00.nycmny13.us.bb.gin.ntt.net
[129.250.2.174]
11 * * * Request timed out.
12 * * * Request timed out ... rinse ... repeat.
Intriguingly, my Plusnet connection (with a TPLink router, not a Plusnet
one) resolves rt.com to 127.0.0.1 (local loopback) on both Windows and
Linux (Raspbian).
That's for the router's DHCP allocating 192.168.1.1 / 208.67.222.222 (OpenDNS) as primary and secondary DNS servers for use by clients, and
the router's WAN connection set to 212.159.6.9 / 212.159.6.10 (Plusnet's DNS). I presume the combination of the two means that it tries
212.159.6.9 first, then 212.159.6.10 and finally 208.67.222.222. (*)
I wonder if some DNS servers have been "poisoned" so they will not
resolve rt.com, and instead "resolve" it to localhost so it fails
gracefully. If I set my Android phone to use Vodafone's mobile internet instead of Plusnet's connection, I can resolve and ping the RT server.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 297 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 10:56:59 |
| Calls: | 6,666 |
| Files: | 12,213 |
| Messages: | 5,336,371 |