Cannot access https://www.tylertech.com/

[#1]

Hi all, 

I'd like to have a chat with our infrastructure team about this, especially given what's been mentioned since I last replied. They don't seem to be available at the moment but I'll do my best to pick this up with them tomorrow. 

Adam 

[#2]

Thanks Adam, it's much appreciated.

[#3]

Not a problem! I'll give you a shout as soon as I've been able to pick this up with them. - Adam 

[#4]

Works fine with my Talktalk connection.

The link in the first post, which is actually https://insidetyler.tylertech.com/ , takes me to a loging page.
https://www.tylertech.com/ takes me to the domains home page.

My tracert arrives at the OP's hops 16 17 so doubt it's anything to do with Plusnets routing.

Tracing route to tylertech.com [207.182.208.157]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  ZyXEL.Home [192.168.1.1]
  2     *        *        *     Request timed out.
  3    20 ms    20 ms    19 ms  host-78-151-229-237.as13285.net [78.151.229.237]
  4    20 ms    20 ms    21 ms  host-78-151-229-240.as13285.net [78.151.229.240]
  5    25 ms     *       25 ms  host-78-144-11-37.as13285.net [78.144.11.37]
  6    25 ms    26 ms    25 ms  ix-ae-8-0.thar1.lrt-london.as6453.net [195.219.100.77]
  7   100 ms   100 ms     *     if-ae-3-2.tcore2.ldn-london.as6453.net [80.231.62.73]
  8    95 ms    94 ms    91 ms  if-ae-32-2.tcore2.nto-new-york.as6453.net [63.243.216.22]
  9    91 ms    90 ms     *     if-ae-9-2.tcore1.n75-new-york.as6453.net [66.110.96.56]
 10    95 ms    93 ms    93 ms  192.205.32.245
 11   100 ms   100 ms   100 ms  cr2.n54ny.ip.att.net [12.122.130.110]
 12   104 ms   100 ms   100 ms  cr1.cb1ma.ip.att.net [12.122.28.134]
 13    97 ms     *       97 ms  12.122.145.73
 14   286 ms   231 ms   215 ms  12.94.2.138
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.

[#5]

LOL. Dude, we've all already confirmed it works with other connections, including EE, BT and My O2 mobile connection. Thanks though.

[#6]

why are plusnet blocking so many websites ? i see a few websites that are being blocked why is this and why arent other internet providers blocking them ?

[#7]

This may or may not be plusnet in this scenario, my office is cooky as well.

[#8]

ok m8 just seen a few people complaining about websites not being reachable and i tried that website and dont work for me but works off my 3 phone internet but wish u well m8 good luck

[#9]

Just in case it helps, it works on my Virgin Media cable connection.

I just get a logon page.

Happy to PM someone my external IP if needed (let me know), probably best I don't post that here I guess.

[#10]

Just keeping this alive. Thanks.

[#11]

If there is someone who is either outside of the UK reading this, or whether someone has access to a VPN maybe they can try a non-UK IP address?

[#12]

Hi there, I didn't get the chance to pick this up again yesterday but I'll do my best to get this looked at before the end of today. 

EDIT: the chaps I need to speak to aren't available so Monday it is, sorry to drag this on but I should be able to pick it up with them then. 

[#13]

---

@Alex wrote:

If there is someone who is either outside of the UK reading this, or whether someone has access to a VPN maybe they can try a non-UK IP address?

---

Using a VPN browser estension I can access it from the USA, European countries and Hong Kong.

[#14]

Bippity Bumpy Bump. (= LOL

[#15 · Accepted solution]

I'm not convinced this is routing.

Like you say, DNS is resolving to the correct IP, and we've already established that  traceroute from a working TalkTalk connection dies at the same place as a traceroute from a non-working Plusnet connection.

I can't access the site either from an external Plusnet line, however the evidence points to it being something at the destination that's causing this.

If you capture what's happening in Wireshark, you can see that we send a TCP SYN to initiate the conversation with the server:

No.     Time           Source                Destination           Protocol Length Info
    430 3.171731       192.168.1.100         207.182.208.157       TCP      66     58101 → 80 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM=1

And the server does reply. However, rather than returning the expected SYN, ACK to acknowledge our request, it's returning a RST, ACK i.e. it's terminating the connection:

No.     Time           Source                Destination           Protocol Length Info
    465 3.273654       207.182.208.157       192.168.1.100         TCP      60     80 → 58101 [RST, ACK] Seq=1 Ack=1 Win=64240 Len=0

This seems to happen almost immediately.

There's also this if I try connecting via a command line using curl:

~ $ curl www.tylertech.com
curl: (7) Failed to connect to www.tylertech.com port 80: Connection refused

To cut to the chase, the administrator of the website in question is probably the person that needs to answer why connection attempts from Plusnet are failing. Incidentally, the line I've tested on also has a static IP in the 80.229.0.0/16 range. Perhaps they're blocking connections for some reason?