# Some servers returning wrong date time

**URL:** <https://community.ntppool.org/t/some-servers-returning-wrong-date-time/1311>\
**Category:** Uncategorized\
**Created:** [July 3, 2019, 7:51am UTC](https://community.ntppool.org/t/some-servers-returning-wrong-date-time/1311 "2019-07-03T07:51:05Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![rjesse](https://avatars.discourse-cdn.com/v4/letter/r/b5e925/32.png) [@rjesse](https://community.ntppool.org/u/rjesse)\
**Post date:** [July 3, 2019, 7:51am UTC](https://community.ntppool.org/t/some-servers-returning-wrong-date-time/1311/1 "2019-07-03T07:51:05Z")

</div>

The server 206.108.0.131 part of [0.pool.ntp.org](http://0.pool.ntp.org) is returning the wrong date and time. Not sure if this is the best place to post this.

 ![Screenshot_20190703-014917_ClockSync](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/1X/d7736243f4f09539d10a19a438014655a63a55c9.jpeg)

---

<div class="post-metadata">

**Author:** ![Hedberg](https://avatars.discourse-cdn.com/v4/letter/h/e95f7d/32.png) [@Hedberg](https://community.ntppool.org/u/Hedberg)\
**Post date:** [July 3, 2019, 8:00am UTC](https://community.ntppool.org/t/some-servers-returning-wrong-date-time/1311/2 "2019-07-03T08:00:13Z")

</div>

If you look at this graph here it seems like it should have been kicket out of the pool automatically:

[https://www.ntppool.org/scores/206.108.0.131](https://www.ntppool.org/scores/206.108.0.131)

---

<div class="post-metadata">

**Author:** ![rjesse](https://avatars.discourse-cdn.com/v4/letter/r/b5e925/32.png) [@rjesse](https://community.ntppool.org/u/rjesse)\
**Post date:** [July 3, 2019, 8:11am UTC](https://community.ntppool.org/t/some-servers-returning-wrong-date-time/1311/3 "2019-07-03T08:11:28Z")

</div>

My servers older nortel phone switch hung onto it and rolled all my clocks back.

---

<div class="post-metadata">

**Author:** ![Hedberg](https://avatars.discourse-cdn.com/v4/letter/h/e95f7d/32.png) [@Hedberg](https://community.ntppool.org/u/Hedberg)\
**Post date:** [July 3, 2019, 9:03am UTC](https://community.ntppool.org/t/some-servers-returning-wrong-date-time/1311/4 "2019-07-03T09:03:59Z")

</div>

I am sorry to hear that. To me it sounds like a poor NTP implementation by Nortel. Most NTP implementations do some kind of sanity checks when it recieves a bad time all of a sudden.

---

<div class="post-metadata">

**Author:** ![Hedberg](https://avatars.discourse-cdn.com/v4/letter/h/e95f7d/32.png) [@Hedberg](https://community.ntppool.org/u/Hedberg)\
**Post date:** [July 3, 2019, 9:33am UTC](https://community.ntppool.org/t/some-servers-returning-wrong-date-time/1311/5 "2019-07-03T09:33:22Z")

</div>

If it is not possible to do any changes to the Nortel phone switch you might want to consider to have it sync time against an internal ntp server that syncs against e.g. 4 different NTP servers. The internal NTP server can then provide the sanity check the Nortel seems to lack.

---

<div class="post-metadata">

**Author:** ![NTPman](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ntpman/32/450_2.png) [@NTPman](https://community.ntppool.org/u/NTPman)\
**Post date:** [July 3, 2019, 9:45am UTC](https://community.ntppool.org/t/some-servers-returning-wrong-date-time/1311/6 "2019-07-03T09:45:44Z")

</div>

> [@rjesse](#):
>
> The server 206.108.0.131 part of [0.pool.ntp.org](http://0.pool.ntp.org) is returning the wrong date and time. Not sure if this is the best place to post this.!

This is [PublicTimeServer001077 \< Servers \< Network Time Foundation's NTP Support Wiki](http://support.ntp.org/bin/view/Servers/PublicTimeServer001077) , part of [ntp.org](http://ntp.org) stratum one server list. They recently changed IPv6 address. For me the refid is .PTP0. , I do not know what kind of device it is.

---

<div class="post-metadata">

**Author:** ![rjesse](https://avatars.discourse-cdn.com/v4/letter/r/b5e925/32.png) [@rjesse](https://community.ntppool.org/u/rjesse)\
**Post date:** [July 3, 2019, 11:24am UTC](https://community.ntppool.org/t/some-servers-returning-wrong-date-time/1311/7 "2019-07-03T11:24:34Z")

</div>

We tried that, the Nortel switch hated our internal ntp servers as they are appliances and the clock floated a bit, very fussy, except they had no problem turning themselves back almost 11 hours against this server… will have to figure out a better way to do the ntp.

---

<div class="post-metadata">

**Author:** ![littlejason99](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/littlejason99/32/242_2.png) [@littlejason99](https://community.ntppool.org/u/littlejason99)\
**Post date:** [July 3, 2019, 12:44pm UTC](https://community.ntppool.org/t/some-servers-returning-wrong-date-time/1311/8 "2019-07-03T12:44:36Z")

</div>

What about using NIST or UNSO time servers?

[https://tf.nist.gov/tf-cgi/servers.cgi](https://tf.nist.gov/tf-cgi/servers.cgi)

[https://tycho.usno.navy.mil/NTP/](https://tycho.usno.navy.mil/NTP/)

---

<div class="post-metadata">

**Author:** ![littlejason99](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/littlejason99/32/242_2.png) [@littlejason99](https://community.ntppool.org/u/littlejason99)\
**Post date:** [July 3, 2019, 12:47pm UTC](https://community.ntppool.org/t/some-servers-returning-wrong-date-time/1311/9 "2019-07-03T12:47:04Z")

</div>

> [@NTPman](#):
>
> They recently changed IPv6 address. For me the refid is .PTP0. , I do not know what kind of device it is.

It’s precision time protocol… Usually those master clocks are high dollar appliances (which use GPS as their time source). I wonder if it was a firmware glitch?

> **[Precision Time Protocol](https://en.wikipedia.org/wiki/Precision_Time_Protocol)**
>
> The Precision Time Protocol (PTP) is a protocol used to synchronize clocks throughout a computer network. On a local area network, it achieves clock accuracy in the sub-microsecond range, making it suitable for measurement and control systems. PTP is employed to synchronize financial transactions, mobile phone tower transmissions, sub-sea acoustic arrays, and networks that require precise timing but lack access to satellite navigation signals.
> The first version of PTP, IEEE 1588-2002, was pub...

---

<div class="post-metadata">

**Author:** ![NTPman](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ntpman/32/450_2.png) [@NTPman](https://community.ntppool.org/u/NTPman)\
**Post date:** [July 3, 2019, 12:54pm UTC](https://community.ntppool.org/t/some-servers-returning-wrong-date-time/1311/10 "2019-07-03T12:54:36Z")

</div>

> [@littlejason99](#):
>
> It’s precision time protocol… Usually those master clocks are high dollar appliances (which use GPS as their time source).

Thanks for the info.

> [@littlejason99](#):
>
> I wonder if it was a firmware glitch?

TORIX support said the problem was due to a software update.

---

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [July 8, 2019, 5:45am UTC](https://community.ntppool.org/t/some-servers-returning-wrong-date-time/1311/11 "2019-07-08T05:45:19Z")

</div>

Hi @rjesse,

Sorry about that! The monitoring system noticed within 15 minutes (which is the current monitoring interval). What time did your client get this IP? The timestamp from your screenshot is unclear.

If you have a google account you should be able to see the [monitoring data](https://console.cloud.google.com/bigquery?sq=846832505602:aee742ea8c61424fb60d95877bfed3de)

I couldn’t figure out to save/export the data from the web UI there, so a paste from ClickHouse below. Only IPs with a score \> 10 are included in the DNS system.

```auto
SELECT
    ts,
    score,
    offset,
    leap,
    error
FROM ntppool.log_scores
WHERE (dt > '2019-07-02') AND (dt < '2019-07-05') AND (server_id = 26543) AND (monitor_id = 0) AND (ts > '2019-07-03 03:27:00') AND (ts < '2019-07-03 20:07:00')
ORDER BY ts ASC

┌──────────────────ts─┬─score─┬────────────offset─┬─leap─┬─error─┐
│ 2019-07-03 03:27:48 │ 20 │ -0.000226408 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 03:45:38 │ 20 │ -0.000164679 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 04:00:40 │ 20 │ -0.000213216 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 04:15:51 │ -20 │ -123315.967782686 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 04:30:52 │ -23 │ -123288.944592952 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 04:46:17 │ -25.8 │ -123261.219792082 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 05:02:16 │ -28.6 │ -123232.459244292 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 05:17:23 │ -31.1 │ -123205.252172915 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 05:33:23 │ -33.6 │ -123176.483727383 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 05:49:30 │ -35.9 │ -123147.48698494 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 06:05:10 │ -38.1 │ -123119.301477879 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 06:21:00 │ -40.2 │ -123090.795084846 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 06:36:48 │ -42.2 │ -123062.39459855 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 06:53:06 │ -44.1 │ -123033.071625305 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 07:08:26 │ -45.9 │ -123005.477039236 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 07:23:53 │ -47.6 │ -122977.665673567 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 07:39:38 │ -49.2 │ -122949.345680211 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 07:55:25 │ -50.7 │ -122920.934713807 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 08:10:52 │ -52.2 │ -122893.149171026 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 08:27:04 │ -53.6 │ -122864.0181016 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 08:42:37 │ -54.9 │ -122836.016033953 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 08:57:46 │ -51.2 │ -0.000075148 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 09:13:15 │ -47.6 │ -0.000089192 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 09:29:11 │ -44.2 │ -0.000160807 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 09:45:48 │ -41 │ -0.000086038 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 10:01:33 │ -38 │ -0.000140129 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 10:17:28 │ -35.1 │ -0.000084247 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 10:33:08 │ -32.3 │ -0.000062954 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 10:48:32 │ -29.7 │ -0.000128317 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 11:04:18 │ -27.2 │ -0.000129007 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 11:20:33 │ -24.9 │ -0.000088187 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 11:36:39 │ -22.6 │ -0.00009082 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 11:52:37 │ -20.5 │ -0.000098353 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 12:08:10 │ -18.5 │ -0.000134241 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 12:24:51 │ -16.5 │ -0.000132269 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 12:40:06 │ -14.7 │ -0.000136365 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 12:55:46 │ -13 │ -0.000026009 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 13:11:57 │ -11.3 │ -0.000024884 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 13:28:46 │ -9.8 │ -0.000128862 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 13:43:57 │ -8.3 │ -0.000050585 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 14:00:28 │ -6.9 │ 0.00002361 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 14:16:16 │ -5.5 │ -0.000021674 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 14:31:19 │ -4.2 │ -0.000118724 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 14:46:28 │ -3 │ -0.000010643 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 15:01:38 │ -1.9 │ -0.000067724 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 15:17:08 │ -0.8 │ -0.000128064 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 15:32:18 │ 0.3 │ -0.00003859 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 15:47:24 │ 1.2 │ -0.000119763 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 16:02:28 │ 2.2 │ -0.000055894 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 16:17:30 │ 3.1 │ -0.000142324 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 16:32:32 │ 3.9 │ -0.000123353 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 16:48:06 │ 4.7 │ -0.000087404 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 17:03:08 │ 5.5 │ -0.000056271 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 17:18:16 │ 6.2 │ -0.000051532 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 17:33:19 │ 6.9 │ -0.000093759 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 17:48:27 │ 7.6 │ -0.000020233 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 18:03:35 │ 8.2 │ -0.000120578 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 18:18:41 │ 8.8 │ -0.000094847 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 18:33:44 │ 9.3 │ -0.000040007 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 18:48:51 │ 9.9 │ -0.000138352 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 19:03:57 │ 10.4 │ -0.000129279 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 19:19:05 │ 10.9 │ -0.000115656 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 19:34:15 │ 11.3 │ 0.000172799 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 19:51:41 │ 11.7 │ -0.000124121 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
│ 2019-07-03 20:06:58 │ 12.2 │ -0.000102116 │ ᴺᵁᴸᴸ │ ᴺᵁᴸᴸ │
└─────────────────────┴───────┴───────────────────┴──────┴───────┘

65 rows in set. Elapsed: 0.031 sec. Processed 49.47 thousand rows, 1.13 MB (1.60 million rows/s., 36.31 MB/s.)

```