cancel
Showing results for 
Search instead for 
Did you mean: 

Plusnet time server down

nw71
Newbie
Posts: 2
Registered: 06-07-2017

Plusnet time server down

The Plusnet time server seems to be down.

This can cause a problem if like me you use your router to schedule internet services to individual devices on you network e.g. setting access control times for kid's iPads / phones etc or to schedule timing for the whole of your wireless network 

 

The server at ntp.plus.net is not working therefore the time control features of the router will fail

In order to restore the access control you need to enter another time server such as 0.uk.pool.ntp.org (you can add up to 6)

 

Hope this is useful - my kids were up late browsing last night and were a nightmare to get out of bed and up for school this morning!Shocked

23 REPLIES
RichardB
Pro
Posts: 299
Thanks: 69
Fixes: 3
Registered: 19-11-2008

Re: Plusnet time server down

Hi nw71,

 

Which PN NTP server are you using?

I am using 212.159.6.10 in my router to synch the time and it seems to be OK currently.

 

Richard

 

nw71
Newbie
Posts: 2
Registered: 06-07-2017

Re: Plusnet time server down

Hi,

 

My router is a Technicolor TG582n FTTC and was set to use ntp.plus.net - i don't know the ip address

I have never had a problem with it for the two years we've had it but it has been failing to sync for the last two days

I have tried several different ntp servers eg

ntp2a.mcc.ac.uk

ntp.exnet.com 

0.uk.pool.ntp.org

 

and they all work fine, just not the plusnet one (maybe it's local to lancashire?)

 

Cheers,

Neil

RichardB
Pro
Posts: 299
Thanks: 69
Fixes: 3
Registered: 19-11-2008

Re: Plusnet time server down

As a test I installed the clock synch app on my android phone.

Set the NTP server to ntp.plus.net and it worked time was displayed correctly with no errors reported.

To double check I set the ntp server to ntp.plus.not and the app reported that the server could not be found.

Not sure if it is a conclusive test but ntp.plus.net seems to work for me.

 

Richard

Browni
Seasoned Champion
Posts: 1,501
Thanks: 424
Fixes: 35
Registered: 02-03-2016

Re: Plusnet time server down

I use ntp.plus.net as a ping target for a speed tester I run and I haven't seen any outages recently.
I must have been really bad in a previous life. This is my 3rd ISP in a row that uses lithium.
Plusnet Help Team
Plusnet Help Team
Posts: 3,992
Thanks: 844
Fixes: 206
Registered: 21-04-2017

Re: Plusnet time server down

I've checked with our network team and I can confirm that our NTP servers are working correctly.

If this post resolved your issue please click the 'This fixed my problem' button
 Anoush Mortazavi
 Plusnet Help Team
Community Veteran
Posts: 4,915
Thanks: 335
Fixes: 16
Registered: 10-06-2010

Re: Plusnet time server down

It appears I haven't been able to access the NTP service on ntp.plus.net since July 7 also.

Perhaps the NTP servers themselves may be running fine, but some customers can't access that service on them?

ntp.plus.net resolves to the same 4 IP addresses as the DNS servers, pinging them and DNS services still work.

seebee
Newbie
Posts: 1
Registered: 08-07-2017

Re: Plusnet time server down

Plusnet time servers don't seem to be working for me either:

pi@rPi3:~ $ ntpdate -d ntp.plus.net
 8 Jul 18:55:35 ntpdate[20172]: ntpdate 4.2.6p5@1.2349-o Mon Jul 25 22:35:35 UTC 2016 (1)
transmit(212.159.6.9)
transmit(212.159.6.10)
transmit(212.159.13.50)
transmit(212.159.13.49)
transmit(212.159.6.9)
transmit(212.159.6.10)
transmit(212.159.13.50)
transmit(212.159.13.49)
transmit(212.159.6.9)
transmit(212.159.6.10)
transmit(212.159.13.50)
transmit(212.159.13.49)
transmit(212.159.6.9)
transmit(212.159.6.10)
transmit(212.159.13.50)
transmit(212.159.13.49)
transmit(212.159.6.9)
transmit(212.159.6.10)
transmit(212.159.13.50)
transmit(212.159.13.49)
212.159.6.9: Server dropped: no data
212.159.6.10: Server dropped: no data
212.159.13.50: Server dropped: no data
212.159.13.49: Server dropped: no data
server 212.159.6.9, port 123
stratum 0, precision 0, leap 00, trust 000
refid [212.159.6.9], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time:    00000000.00000000  Thu, Feb  7 2036  6:28:16.000
originate timestamp: 00000000.00000000  Thu, Feb  7 2036  6:28:16.000
transmit timestamp:  dd0b9b1e.11043c0b  Sat, Jul  8 2017 18:55:42.066
filter delay:  0.00000  0.00000  0.00000  0.00000
         0.00000  0.00000  0.00000  0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
         0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000

server 212.159.6.10, port 123
stratum 0, precision 0, leap 00, trust 000
refid [212.159.6.10], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time:    00000000.00000000  Thu, Feb  7 2036  6:28:16.000
originate timestamp: 00000000.00000000  Thu, Feb  7 2036  6:28:16.000
transmit timestamp:  dd0b9b1e.443da488  Sat, Jul  8 2017 18:55:42.266
filter delay:  0.00000  0.00000  0.00000  0.00000
         0.00000  0.00000  0.00000  0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
         0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000

server 212.159.13.50, port 123
stratum 0, precision 0, leap 00, trust 000
refid [212.159.13.50], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time:    00000000.00000000  Thu, Feb  7 2036  6:28:16.000
originate timestamp: 00000000.00000000  Thu, Feb  7 2036  6:28:16.000
transmit timestamp:  dd0b9b1e.77627d38  Sat, Jul  8 2017 18:55:42.466
filter delay:  0.00000  0.00000  0.00000  0.00000
         0.00000  0.00000  0.00000  0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
         0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000

server 212.159.13.49, port 123
stratum 0, precision 0, leap 00, trust 000
refid [212.159.13.49], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time:    00000000.00000000  Thu, Feb  7 2036  6:28:16.000
originate timestamp: 00000000.00000000  Thu, Feb  7 2036  6:28:16.000
transmit timestamp:  dd0b9b1e.aa945d37  Sat, Jul  8 2017 18:55:42.666
filter delay:  0.00000  0.00000  0.00000  0.00000
         0.00000  0.00000  0.00000  0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
         0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000

 8 Jul 18:55:44 ntpdate[20172]: no server suitable for synchronization found

Whilst other NTP servers are okay:

pi@rPi3:~ $ ntpdate -d uk.pool.ntp.org
 8 Jul 18:56:58 ntpdate[20174]: ntpdate 4.2.6p5@1.2349-o Mon Jul 25 22:35:35 UTC 2016 (1)
transmit(176.58.109.199)
receive(176.58.109.199)
transmit(129.250.35.250)
receive(129.250.35.250)
transmit(85.199.214.101)
receive(85.199.214.101)
transmit(185.114.227.160)
transmit(176.58.109.199)
transmit(129.250.35.250)
receive(129.250.35.250)
transmit(85.199.214.101)
receive(85.199.214.101)
transmit(185.114.227.160)
receive(185.114.227.160)
transmit(176.58.109.199)
receive(176.58.109.199)
transmit(129.250.35.250)
receive(129.250.35.250)
transmit(85.199.214.101)
receive(85.199.214.101)
transmit(185.114.227.160)
transmit(176.58.109.199)
receive(176.58.109.199)
transmit(129.250.35.250)
receive(129.250.35.250)
transmit(85.199.214.101)
receive(85.199.214.101)
transmit(185.114.227.160)
transmit(185.114.227.160)
server 176.58.109.199, port 123
stratum 2, precision -22, leap 00, trust 000
refid [176.58.109.199], delay 0.03864, dispersion 8.00011
transmitted 4, in filter 4
reference time:    dd0b9770.47a5faaf  Sat, Jul  8 2017 18:40:00.279
originate timestamp: dd0b9b70.bd112f34  Sat, Jul  8 2017 18:57:04.738
transmit timestamp:  dd0b9b70.bb2c836b  Sat, Jul  8 2017 18:57:04.731
filter delay:  0.03871  0.00000  0.04074  0.03864
         0.00000  0.00000  0.00000  0.00000
filter offset: 0.000781 0.000000 0.000543 0.000865
         0.000000 0.000000 0.000000 0.000000
delay 0.03864, dispersion 8.00011
offset 0.000865

server 129.250.35.250, port 123
stratum 2, precision -20, leap 00, trust 000
refid [129.250.35.250], delay 0.03790, dispersion 0.00023
transmitted 4, in filter 4
reference time:    dd0b9b5a.2451c9b1  Sat, Jul  8 2017 18:56:42.141
originate timestamp: dd0b9b70.f0438d08  Sat, Jul  8 2017 18:57:04.938
transmit timestamp:  dd0b9b70.ee5d4f48  Sat, Jul  8 2017 18:57:04.931
filter delay:  0.03809  0.03802  0.03790  0.03824
         0.00000  0.00000  0.00000  0.00000
filter offset: 0.000957 0.001073 0.000760 0.001098
         0.000000 0.000000 0.000000 0.000000
delay 0.03790, dispersion 0.00023
offset 0.000760

server 85.199.214.101, port 123
stratum 1, precision -25, leap 00, trust 000
refid [GPS], delay 0.03929, dispersion 0.00012
transmitted 4, in filter 4
reference time:    dd0b9b71.00000000  Sat, Jul  8 2017 18:57:05.000
originate timestamp: dd0b9b71.238ee1bd  Sat, Jul  8 2017 18:57:05.138
transmit timestamp:  dd0b9b71.218eb253  Sat, Jul  8 2017 18:57:05.131
filter delay:  0.03943  0.03929  0.04060  0.03955
         0.00000  0.00000  0.00000  0.00000
filter offset: 0.000734 0.000878 0.000340 0.000841
         0.000000 0.000000 0.000000 0.000000
delay 0.03929, dispersion 0.00012
offset 0.000878

server 185.114.227.160, port 123
stratum 2, precision -20, leap 00, trust 000
refid [185.114.227.160], delay 0.04491, dispersion 56.00000
transmitted 4, in filter 4
reference time:    dd0b9849.259454b3  Sat, Jul  8 2017 18:43:37.146
originate timestamp: dd0b9b6d.574b4ebe  Sat, Jul  8 2017 18:57:01.340
transmit timestamp:  dd0b9b71.54c04109  Sat, Jul  8 2017 18:57:05.331
filter delay:  0.00000  0.04491  0.00000  0.00000
         0.00000  0.00000  0.00000  0.00000
filter offset: 0.000000 0.000121 0.000000 0.000000
         0.000000 0.000000 0.000000 0.000000
delay 0.04491, dispersion 56.00000
offset 0.000121

 8 Jul 18:57:07 ntpdate[20174]: adjust time server 85.199.214.101 offset 0.000878 sec

The Plusnet time servers are replying to pings okay:

pi@rPi3:~ $ ping -c 5 ntp.plus.net
PING ntp.plus.net (212.159.6.9) 56(84) bytes of data.
64 bytes from cdns01.plus.net (212.159.6.9): icmp_seq=1 ttl=60 time=11.5 ms
64 bytes from cdns01.plus.net (212.159.6.9): icmp_seq=2 ttl=60 time=11.1 ms
64 bytes from cdns01.plus.net (212.159.6.9): icmp_seq=3 ttl=60 time=21.4 ms
64 bytes from cdns01.plus.net (212.159.6.9): icmp_seq=4 ttl=60 time=14.9 ms
64 bytes from cdns01.plus.net (212.159.6.9): icmp_seq=5 ttl=60 time=11.2 ms

--- ntp.plus.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 11.198/14.061/21.412/3.943 ms
pi@rPi3:~ $ ping -c 5 ntp.plus.net
PING ntp.plus.net (212.159.13.49) 56(84) bytes of data.
64 bytes from cdns01.plus.net (212.159.13.49): icmp_seq=1 ttl=60 time=10.4 ms
64 bytes from cdns01.plus.net (212.159.13.49): icmp_seq=2 ttl=60 time=13.0 ms
64 bytes from cdns01.plus.net (212.159.13.49): icmp_seq=3 ttl=60 time=13.3 ms
64 bytes from cdns01.plus.net (212.159.13.49): icmp_seq=4 ttl=60 time=11.1 ms
64 bytes from cdns01.plus.net (212.159.13.49): icmp_seq=5 ttl=60 time=10.8 ms

--- ntp.plus.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 10.473/11.781/13.371/1.187 ms

This is all on a Raspberry PI, but I've also tried using it as a time server in windows 10 and it doesn't respond then either.

Perhaps it depends on the source IP which is why others dont see a problem. My Plusnet IP is currently 51.9.132.x but I also tried from a Debian machine in America (from IP 199.175.48.x) and got exactly the same - ntp.plus.net is not replying to NTP requests (but is replying to pings) whilst other NTP servers are replying okay.

Superuser
Superuser
Posts: 9,974
Thanks: 1,504
Fixes: 20
Registered: 22-08-2007

Re: Plusnet time server down

Looks like different users are having different experiences. I'm on a fixed IP and still have full connectivity to the time servers. From my router log.

Jul 8 20:08:46 SNTP Synchronised to server: 212.159.6.9


Info Jul 8 19:08:46 SNTP Synchronised to server: 212.159.13.50


Info Jul 8 18:08:46 SNTP Synchronised again to server: 212.159.6.10

I'm now wondering if gateways, new and old network connectivity have any bearing?
Superuser
Superuser
Posts: 2,579
Thanks: 966
Fixes: 8
Registered: 10-04-2007

Re: Plusnet time server down

Dredging my memory, there was a problem some years back (2010) with the plusnet Firewall defaulting to 'High' causing similar problems.  Tried a search but couldn't find a good reference.  As @Townman suggests has it resurfaced with the new network routing?

 

Community Veteran
Posts: 2,211
Thanks: 95
Fixes: 4
Registered: 18-02-2013

Re: Plusnet time server down

No problems here, static ip 80.229....

 

ntpdate -d ntp.plus.net
6 Feb 02:28:56 ntpdate[3082]: ntpdate 4.2.8p10@1.3728-o Tue Apr 25 07:24:47 UTC 2017 (1)
Looking for host ntp.plus.net and service ntp
212.159.13.50 reversed to cdns02.plus.net
cdns02.plus.net forward check lookup fail: Name or service not known
host found : 212.159.13.50 (cdns02.plus.net)
transmit(212.159.13.50)
receive(212.159.13.50)
transmit(212.159.6.9)
receive(212.159.6.9)
transmit(212.159.13.49)
receive(212.159.13.49)
transmit(212.159.6.10)
receive(212.159.6.10)
transmit(212.159.13.50)
receive(212.159.13.50)
transmit(212.159.6.9)
receive(212.159.6.9)
transmit(212.159.13.49)
receive(212.159.13.49)
transmit(212.159.6.10)
receive(212.159.6.10)
transmit(212.159.13.50)
receive(212.159.13.50)
transmit(212.159.6.9)
receive(212.159.6.9)
transmit(212.159.13.49)
receive(212.159.13.49)
transmit(212.159.6.10)
receive(212.159.6.10)
transmit(212.159.13.50)
receive(212.159.13.50)
transmit(212.159.6.9)
receive(212.159.6.9)
transmit(212.159.13.49)
receive(212.159.13.49)
transmit(212.159.6.10)
receive(212.159.6.10)
server 212.159.13.50, port 123
stratum 2, precision -21, leap 00, trust 000
refid [212.159.13.50], delay 0.03918, dispersion 0.00000
transmitted 4, in filter 4
reference time: dd0bc8c0.621b1036 Sat, Jul 8 2017 15:10:24.383
originate timestamp: dd0bcb60.657f54af Sat, Jul 8 2017 15:21:36.396
transmit timestamp: dc42c05f.0fb69985 Mon, Feb 6 2017 2:29:03.061
filter delay: 0.03929 0.03952 0.03918 0.03946
0.00000 0.00000 0.00000 0.00000
filter offset: 13175553 13175553 13175553 13175553
0.000000 0.000000 0.000000 0.000000
delay 0.03918, dispersion 0.00000
offset 13175553.328176

server 212.159.6.9, port 123
stratum 2, precision -21, leap 00, trust 000
refid [212.159.6.9], delay 0.03903, dispersion 0.00000
transmitted 4, in filter 4
reference time: dd0bc85b.6ecd6f45 Sat, Jul 8 2017 15:08:43.432
originate timestamp: dd0bcb60.98bd4ede Sat, Jul 8 2017 15:21:36.596
transmit timestamp: dc42c05f.42eafab5 Mon, Feb 6 2017 2:29:03.261
filter delay: 0.03903 0.03911 0.03931 0.03946
0.00000 0.00000 0.00000 0.00000
filter offset: 13175553 13175553 13175553 13175553
0.000000 0.000000 0.000000 0.000000
delay 0.03903, dispersion 0.00000
offset 13175553.328377

server 212.159.13.49, port 123
stratum 2, precision -21, leap 00, trust 000
refid [212.159.13.49], delay 0.03918, dispersion 0.00000
transmitted 4, in filter 4
reference time: dd0bc8c0.621b1036 Sat, Jul 8 2017 15:10:24.383
originate timestamp: dd0bcb60.cbe2a0e5 Sat, Jul 8 2017 15:21:36.796
transmit timestamp: dc42c05f.761ec4e7 Mon, Feb 6 2017 2:29:03.461
filter delay: 0.03975 0.03922 0.03943 0.03918
0.00000 0.00000 0.00000 0.00000
filter offset: 13175553 13175553 13175553 13175553
0.000000 0.000000 0.000000 0.000000
delay 0.03918, dispersion 0.00000
offset 13175553.328215

server 212.159.6.10, port 123
stratum 2, precision -21, leap 00, trust 000
refid [212.159.6.10], delay 0.03934, dispersion 0.00000
transmitted 4, in filter 4
reference time: dd0bc5a3.259c646f Sat, Jul 8 2017 14:57:07.146
originate timestamp: dd0bcb60.ff10fbec Sat, Jul 8 2017 15:21:36.996
transmit timestamp: dc42c05f.a9513f8e Mon, Feb 6 2017 2:29:03.661
filter delay: 0.03949 0.03935 0.03934 0.03949
0.00000 0.00000 0.00000 0.00000
filter offset: 13175553 13175553 13175553 13175553
0.000000 0.000000 0.000000 0.000000
delay 0.03934, dispersion 0.00000
offset 13175553.328254

6 Feb 02:29:03 ntpdate[3082]: step time server 212.159.6.9 offset 13175553.3283 77 sec

Community Veteran
Posts: 4,915
Thanks: 335
Fixes: 16
Registered: 10-06-2010

Re: Plusnet time server down


MauriceC wrote:

Dredging my memory, there was a problem some years back (2010) with the plusnet Firewall defaulting to 'High' causing similar problems.  Tried a search but couldn't find a good reference.  As @Townman suggests has it resurfaced with the new network routing?

 


If the Plusnet Broadband Firewall had been set to "High", then each person affected wouldn't have been able to access any NTP services.

mort7890
Rising Star
Posts: 105
Thanks: 12
Registered: 28-06-2007

Re: Plusnet time server down

Just looked into my plusnet hub one and the log shows

19:24:08, 23 Mar. (156261.950000) NTP synchronization failure!

When I look at plusnet access control the current time is "retrieving" and looks like it has been since the 22 Mar.

RichardB
Pro
Posts: 299
Thanks: 69
Fixes: 3
Registered: 19-11-2008

Re: Plusnet time server down

Hi all,

For info:

ntpdate -d ntp.plus.net works OK for me on my RPI. All servers responded.

However, I do have a static IP in the range of 80.229.x.x.

Currently connected to pcn-bng04 just in case it is relevant.

Richard

pvmb
Rising Star
Posts: 263
Thanks: 17
Fixes: 1
Registered: 12-02-2014

Re: Plusnet time server down

Warning Jul 9 11:26:24 SNTP Unable to contact server: 212.159.13.50
Warning Jul 9 10:25:38 SNTP Unable to contact server: 212.159.13.50
Warning Jul 9 09:24:53 SNTP Unable to contact server: 212.159.13.50
Warning Jul 9 08:24:08 SNTP Unable to contact server: 212.159.13.50
Warning Jul 9 07:23:22 SNTP Unable to contact server: 212.159.13.50
Warning Jul 9 06:22:37 SNTP Unable to contact server: 212.159.6.9
Warning Jul 9 05:21:51 SNTP Unable to contact server: 212.159.13.50
Warning Jul 9 04:21:06 SNTP Unable to contact server: 212.159.13.50
Warning Jul 9 03:20:21 SNTP Unable to contact server: 212.159.13.50
Warning Jul 9 02:19:35 SNTP Unable to contact server: 212.159.13.50
Warning Jul 9 01:18:50 SNTP Unable to contact server: 212.159.13.50
Warning Jul 9 00:18:05 SNTP Unable to contact server: 212.159.13.50
Warning Jul 8 23:17:19 SNTP Unable to contact server: 212.159.13.50
Warning Jul 8 22:16:34 SNTP Unable to contact server: 212.159.13.50
Warning Jul 8 21:15:48 SNTP Unable to contact server: 212.159.13.50
Warning Jul 8 20:15:03 SNTP Unable to contact server: 212.159.6.9
Warning Jul 8 19:14:18 SNTP Unable to contact server: 212.159.13.49
Warning Jul 8 18:13:32 SNTP Unable to contact server: 212.159.6.10
Warning Jul 8 17:12:47 SNTP Unable to contact server: 212.159.6.9
Warning Jul 8 16:12:01 SNTP Unable to contact server: 212.159.6.10
Warning Jul 8 15:11:16 SNTP Unable to contact server: 212.159.6.10
Warning Jul 8 14:10:31 SNTP Unable to contact server: 212.159.6.10
Warning Jul 8 13:09:45 SNTP Unable to contact server: 212.159.6.9
Warning Jul 8 12:09:00 SNTP Unable to contact server: 212.159.6.10
Warning Jul 8 11:08:15 SNTP Unable to contact server: 212.159.13.49