Full List of NTP Peers, Leap Second 2008

0.0.0.0

Mix of IPv6 clients - no large offsets, so it looks like it all went well.

127.127.1.1

Local clock - nothing to see here.

127.127.20.0

Our GPS refclock - looks like we latched on to the wrong second pulse after the leap second, and this fixed itself up when the GPS receiver next lost sync. However, it was identified as a falseticker and so didn't cause problems.

128.4.1.1

Rackety was well behaved, as expected.

129.132.2.21

Some wobbles in swisstime, but no leap second misbehaviour.

134.226.1.114

We lost a few packets talking to this TCD peer, but there are no big jumps around the leap second.

134.226.109.127

This TCD client looks like it got it wrong, and probably steped the clock to fix things.

134.226.145.76

This TCD client looks like it got it wrong and then slewed the clock to fix things.

134.226.32.57

This TCD peer seems to have done the right thing.

140.203.16.5

This is a peer in Galway that does the right thing, though there are some strange blips in the jitter. It has a GPS refclock, so this may be the signal comming and goint there.

149.6.4.100

This machine looks like it does the wrong thing and then steps to fix.

159.134.93.132

The step in this peer looks like it is due to an exceptionally delayed packet rather than the leap second.

193.1.172.140

Peer in UCD - seems well behaved.

193.120.136.165

Some spikes in the delay here, but nothing much suspicious in the offsets.

193.138.128.67

This peer looks like it gets it wrong and then oversteps on the way back.

194.125.58.134

This peer probably got it wrong and stepped, but we aren't seeing enough samples to really be sure.

195.11.99.249

Some oddities here after the leap, but they seem to be RTT related.

195.166.155.129

This peer has some odd behaviour, and seems to wind up off by a bit over half a second for a while.

195.239.238.171

This peer seems to decide to sit at about -100ms (maybe it's behind a link with asymetric load with an internal source of time) and goes back to that after getting the leap wrong by slewing the clock.

195.7.49.1

This peer is so badly behaved it is hard to know what's actually going on.

195.7.57.199

Looks like a well behaved peer with a RTT spike.

212.100.105.250

Usually seems well behaved, bar some RTT spikes.

212.170.106.137

Looks generally badly behaved.

212.38.80.162

Looks like leap second was missed and then stepped back.

212.66.70.200

Very well behaved looking peer.

213.161.69.135

Well behaved peer with interesting diurnal behaviour.

213.200.94.194

Woh!

213.94.137.74

No problems here.

217.34.206.230

This actually looks like routing problems rather than leap second.

217.41.4.153

Another routing spike, but no obvious leap second problems.

217.75.9.225

Spike, no leap.

4.79.80.253

Probably a leap second related blip?

62.213.4.26

A jump followed by decay to the previous value. Interesting long term behaviour too.

62.77.186.129

Pretty well behaved peer.

62.93.189.50

Another well behaved peer.

78.46.64.15

Probably does something bad for the leap second, but it pretty erratically behaved at the best of times.

79.97.234.149

Another pretty confused machine.

80.177.192.242

Pretty well behaved, certainly no leap blips.

81.3.140.154

Looks like a missing leap followed by a step to correct.

82.141.226.147

Probably actually a routing blip?

82.141.238.49

Very weird - no leap blip, but the host seems to be getting further and further away!

82.141.251.74

The delay for this one looks weird, but there is a jump of 500ms near the leap - could be related to delay asymetry somehow though.

83.104.181.210

Looks like a reasonably well behaved peer, bar the big asymetric rtt about a day before the leap.

83.147.147.9

This one looks like it began to wander off in the wrong direction!

83.71.188.202

Seems well behaved.

84.12.39.139

This host shows odd delay spurts, but there may be a leap realted jump too.

84.203.120.38

Looks like it was well synced and then missed the leap.

84.203.210.178

A leap followed by a damped oscilation. Interestingly, the delay jumps after the leap.

85.139.176.170

Looks like a step half a second in the wrong direction!

85.189.184.114

Just looks like a rtt bump for this one.

86.143.189.53

I think this one missed the leap, but usually has a offset anyway.

86.169.176.181

No problems with the leap here, but clear problems with asymetric round trips.

87.41.10.10

There's rather a lot of points on this, maybe multiple machines? Looks like one missed the leap though.

87.42.62.2

Similar to the last one.

89.100.220.54

Looks like a little leap-related purturbation.

91.142.111.169

Lots of delay spikes here, but nothing leap realted.

91.77.152.88

Slowly wandering around with a big jump for the leap.

91.84.131.70

Another machine getting further and further away...

91.84.45.190

Not enough points to say what's going on.