DNS response history for ns2.gzkjby.com

ns2.gzkjby.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-27. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 466 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 ns2.gzkjby.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

466 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.79.124.133

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.gzkjby.com

Showing DNS history for 2026-08-27 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
34 2026-08-27 10:58 639234243654907465
351 ms 51.79.124.133
33 2026-08-27 10:41 639234233269654413
230 ms 51.79.124.133
32 2026-08-27 10:24 639234222943951923
347 ms 51.79.124.133
31 2026-08-27 10:07 639234212558002823
2228 ms 51.79.124.133
30 2026-08-27 09:49 639234202117531850
241 ms 51.79.124.133
29 2026-08-27 09:32 639234191649612722
346 ms 51.79.124.133
28 2026-08-27 09:14 639234181105879568
348 ms 51.79.124.133
27 2026-08-27 08:57 639234170713214496
2308 ms 51.79.124.133
26 2026-08-27 08:40 639234160341037652
351 ms 51.79.124.133
25 2026-08-27 08:22 639234149799404224
351 ms 51.79.124.133
24 2026-08-27 08:04 639234139553286469
350 ms 51.79.124.133
23 2026-08-27 07:11 639234107183588293
238 ms 51.79.124.133
22 2026-08-27 06:54 639234096905435724
234 ms 51.79.124.133
21 2026-08-27 06:37 639234086579410775
356 ms 51.79.124.133
20 2026-08-27 06:19 639234076291157956
346 ms 51.79.124.133
19 2026-08-27 06:02 639234065981939454
349 ms 51.79.124.133
18 2026-08-27 05:45 639234055548642997
2216 ms 51.79.124.133
17 2026-08-27 05:28 639234045267979603
351 ms 51.79.124.133
16 2026-08-27 05:11 639234034999717463
229 ms 51.79.124.133
15 2026-08-27 04:53 639234024739225358
353 ms 51.79.124.133
14 2026-08-27 04:36 639234014311170162
233 ms 51.79.124.133
13 2026-08-27 04:19 639234003806017640
356 ms 51.79.124.133
12 2026-08-27 04:01 639233993356203030
228 ms 51.79.124.133
11 2026-08-27 03:08 639233961301716608
348 ms 51.79.124.133
10 2026-08-27 02:51 639233950834200647
346 ms 51.79.124.133
9 2026-08-27 02:33 639233940431849026
238 ms 51.79.124.133
8 2026-08-27 02:16 639233930110596398
342 ms 51.79.124.133
7 2026-08-27 01:59 639233919705434540
351 ms 51.79.124.133
6 2026-08-27 01:42 639233909452807845
232 ms 51.79.124.133
5 2026-08-27 01:24 639233899096420820
2 ms 51.79.124.133
4 2026-08-27 01:07 639233888707824939
2 ms 51.79.124.133
3 2026-08-27 00:50 639233878461203802
347 ms 51.79.124.133
2 2026-08-27 00:32 639233868060868209
358 ms 51.79.124.133
1 2026-08-27 00:15 639233857450922991
349 ms 51.79.124.133