DNS response history for gtmhen.paychex.com

gtmhen.paychex.com is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-26. For this date, NameServerHistory found 37 DNS check records, 36 successful responses, 1 failed responses, and 249 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for gtmhen.paychex.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

249 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

141.123.119.1

Most recently resolved hosting IP on selected date

Successful Responses

36

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for gtmhen.paychex.com

Showing DNS history for 2026-08-26 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
37 2026-08-26 12:21 639233434974187439
21 ms 141.123.119.1
36 2026-08-26 12:04 639233424567558554
310 ms 141.123.119.1
35 2026-08-26 11:46 639233414056832719
22 ms 141.123.119.1
34 2026-08-26 11:29 639233403515141099
9 ms 141.123.119.1
33 2026-08-26 10:34 639233370841350248
2027 ms 141.123.119.1
32 2026-08-26 10:17 639233360361507238
4 ms 141.123.119.1
31 2026-08-26 10:00 639233350067824371
42 ms 141.123.119.1
30 2026-08-26 09:42 639233339545274518
27 ms 141.123.119.1
29 2026-08-26 09:25 639233329214918079
6 ms 141.123.119.1
28 2026-08-26 09:08 639233318749762337
14 ms 141.123.119.1
27 2026-08-26 08:50 639233308387917838
5 ms 141.123.119.1
26 2026-08-26 08:33 639233297961740122
4 ms 141.123.119.1
25 2026-08-26 08:15 639233287487159094
10 ms 141.123.119.1
24 2026-08-26 07:58 639233276995531707
20 ms 141.123.119.1
23 2026-08-26 07:40 639233266521568229
7 ms 141.123.119.1
22 2026-08-26 07:23 639233256081047431
22 ms 141.123.119.1
21 2026-08-26 06:29 639233223620132921
8 ms 141.123.119.1
20 2026-08-26 06:12 639233213287814244
4 ms 141.123.119.1
19 2026-08-26 05:54 639233202925983161
38 ms 141.123.119.1
18 2026-08-26 05:37 639233192644780696
28 ms 141.123.119.1
17 2026-08-26 05:20 639233182401183833
2032 ms 141.123.119.1
16 2026-08-26 05:03 639233172074181051
5 ms 141.123.119.1
15 2026-08-26 04:46 639233161808421455
5 ms 141.123.119.1
14 2026-08-26 04:28 639233151357344052
17 ms 141.123.119.1
13 2026-08-26 04:11 639233141034116946
38 ms 141.123.119.1
12 2026-08-26 03:54 639233130828334142
36 ms 141.123.119.1
11 2026-08-26 03:37 639233120373450007
3 ms 141.123.119.1
10 2026-08-26 03:20 639233110066216193
25 ms 141.123.119.1
9 2026-08-26 02:26 639233078065410564
23 ms 141.123.119.1
8 2026-08-26 02:09 639233067787457832
2018 ms 141.123.119.1
7 2026-08-26 01:52 639233057501801162
22 ms 141.123.119.1
6 2026-08-26 01:35 639233047089431703
21 ms 141.123.119.1
5 2026-08-26 01:18 639233036754790688
-
4 2026-08-26 01:00 639233026412602472
24 ms 141.123.119.1
3 2026-08-26 00:43 639233016064066127
30 ms 141.123.119.1
2 2026-08-26 00:26 639233005922655772
17 ms 141.123.119.1
1 2026-08-26 00:09 639232995672256907
2026 ms 141.123.119.1