NITLC Student Net Site...down again!!!

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hi all,

Is it me or is NITLC's Student Net Site always down over the weekends? I'm starting to get the feeling that they exceed their bandwidth every 5 days or only pay for 5 days worth !

Strange!

Sacha

 

Well I'm still getting page cannot be displayed?

I've flushed my resolver cache but still no show? Heres what I've done so far:

C:\Documents and Settings\Sacha>nslookup studentnet.nitlc.com
Server: ns1-wol.blueyonder.net
Address: 62.31.176.39

Non-authoritative answer:
Name: war.nitlc.com
Address: 217.46.150.169
Aliases: studentnet.nitlc.com

The above suggests that Telewests DNS server is "up and running". Below is a tracert:

C:\Documents and Settings\Sacha>tracert studentnet.nitlc.com

Tracing route to war.nitlc.com [217.46.150.169]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 11 ms 10 ms 10.18.192.1
3 9 ms 10 ms 9 ms gsr01-br.blueyonder.co.uk [62.31.176.1]
4 10 ms 9 ms 10 ms 172.18.4.65
5 14 ms 38 ms 16 ms 194.117.136.134
6 14 ms 15 ms 17 ms bt-telewest-privatepeer.blueyonder.co.uk [194.11
7.147.18]
7 15 ms 15 ms 15 ms core1-pos14-0.ilford.ukcore.bt.net [194.74.65.11
8]
8 18 ms 17 ms 16 ms core1-pos5-3.bletchley.ukcore.bt.net [195.99.120
.214]
9 18 ms 18 ms 17 ms interconnect2-pos4-0.bletchley.fixed.bt.net [194
.72.31.42]
10 17 ms 16 ms 17 ms ftip002606859.interconnect2.bletchley.fixed-nte.
bt.net [213.120.62.202]
11 19 ms 20 ms 19 ms 213.120.62.34
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.

At this time of writing I still can't get in? Every weekend this happens...

Can't be Telewest surely? But seeing that its a non authoritive answer it could be a problem with the Telewest DNS servers cache! Perhaps the cached NS server for NITLC is down and another is being used thus making the cached result on the TW DNS server out of date...who knows...

Cheers

Sacha (only one "S" and one small "c")

 

I just used Ping Plotter to trace the address and got the following

We are on different networks so will more than likely follow different routes but the last address that responds to your tracert is in my route to NITLC too, it looks as though there are 3 more hops after that address before NITLC. My guess would be a problem within those last 3 hops rather than at NITLC's end.