I've been receiving reports and after testing it appears timestamp.verisign.com is not responding. Wanted to pass the note around in case others are trying to figure out why tools using this service may be failing. Resolves same IP east or west coast. timestamp.verisign.com is an alias for timestamp.ilg.ws.symantec.net. timestamp.ilg.ws.symantec.net has address 69.58.181.58 I don't know how far into the network this trace usually goes but here it is anyway: traceroute to timestamp.ilg.ws.symantec.net (69.58.181.58), 30 hops max, 38 byte packets 1 dsl017-116-125.spk0.dsl.speakeasy.net (69.17.116.125) 0.418 ms 0.354 ms 0.322 ms 2 151.ge-1-3-9.cr1.sea1.speakeasy.net (69.17.82.49) 0.515 ms 0.265 ms 0.267 ms 3 h-64-105-252-17.sttn.wa.megapath.net (64.105.252.17) 0.576 ms 0.590 ms 0.572 ms 4 h-68-165-130-118.sttn.wa.megapath.net (68.165.130.118) 2.947 ms 2.606 ms 1.878 ms 5 ae0-0.sttlwawb-mxc1.bb.megapath.net (155.229.57.85) 2.933 ms 4.521 ms 4.261 ms 6 ae2-0.snvacaid-mxc1.bb.megapath.net (155.229.101.94) 32.576 ms 30.025 ms 26.090 ms 7 ae0-0.snvacaid-mxc2.bb.megapath.net (155.229.57.14) 28.291 ms 26.311 ms 25.274 ms 8 ge-2-1-0-0.c01.pao.bb.megapath.net (155.229.70.222) 26.580 ms 26.610 ms 26.319 ms 9 ge-1-1-0-10.c00.pao.bb.megapath.net (155.229.120.33) 27.448 ms 27.268 ms 26.211 ms 10 xe-1-1-0.r1.bb-fo.sfo1.vrsn.net (198.32.176.30) 26.816 ms 43.217 ms 25.306 ms 11 199.16.95.146 (199.16.95.146) 25.912 ms 25.473 ms 26.247 ms 12 * 199.7.78.126 (199.7.78.126) 25.265 ms 25.420 ms 13 * * * 14 * * * 15 * Thanks, - DL