DNS response history for ns2.yanjinpuzi.com

ns2.yanjinpuzi.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-25. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 1275 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.yanjinpuzi.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

1275 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

111.22.160.86

Most recently resolved hosting IP on selected date

Successful Responses

37

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.yanjinpuzi.com

Showing DNS history for 2026-08-25 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-25 12:43 639232576780683689
1092 ms 111.22.160.86
36 2026-08-25 12:26 639232566381512620
1119 ms 111.22.160.86
35 2026-08-25 12:09 639232556111768563
1126 ms 111.22.160.86
34 2026-08-25 11:51 639232545839529039
1148 ms 111.22.160.86
33 2026-08-25 11:34 639232535349285207
1137 ms 111.22.160.86
32 2026-08-25 11:17 639232524938080723
1124 ms 111.22.160.86
31 2026-08-25 10:23 639232492740373468
1164 ms 111.22.160.86
30 2026-08-25 10:06 639232482235303141
1115 ms 111.22.160.86
29 2026-08-25 09:48 639232471861770303
1128 ms 111.22.160.86
28 2026-08-25 09:31 639232461630217327
1478 ms 111.22.160.86
27 2026-08-25 09:14 639232451282965990
1129 ms 111.22.160.86
26 2026-08-25 08:57 639232440814614938
1146 ms 111.22.160.86
25 2026-08-25 08:39 639232430410720425
1178 ms 111.22.160.86
24 2026-08-25 08:22 639232420003096185
1507 ms 111.22.160.86
23 2026-08-25 08:05 639232409467287444
1123 ms 111.22.160.86
22 2026-08-25 07:47 639232399077195997
1124 ms 111.22.160.86
21 2026-08-25 07:30 639232388731528337
1146 ms 111.22.160.86
20 2026-08-25 07:12 639232378288598612
1129 ms 111.22.160.86
19 2026-08-25 06:18 639232346196373643
1122 ms 111.22.160.86
18 2026-08-25 06:02 639232336112370741
1134 ms 111.22.160.86
17 2026-08-25 05:45 639232326146508970
1153 ms 111.22.160.86
16 2026-08-25 05:28 639232316189381720
1136 ms 111.22.160.86
15 2026-08-25 05:12 639232306217998913
5612 ms 111.22.160.86
14 2026-08-25 04:55 639232296255744174
1125 ms 111.22.160.86
13 2026-08-25 04:38 639232286095760789
1116 ms 111.22.160.86
12 2026-08-25 04:21 639232276086186273
1093 ms 111.22.160.86
11 2026-08-25 04:05 639232265900986425
1146 ms 111.22.160.86
10 2026-08-25 03:48 639232255723518075
1114 ms 111.22.160.86
9 2026-08-25 03:31 639232245484452890
1453 ms 111.22.160.86
8 2026-08-25 03:14 639232235157175331
1123 ms 111.22.160.86
7 2026-08-25 02:20 639232203197189095
1088 ms 111.22.160.86
6 2026-08-25 02:03 639232192844564298
1139 ms 111.22.160.86
5 2026-08-25 01:46 639232182496008942
1099 ms 111.22.160.86
4 2026-08-25 01:29 639232172197053132
1089 ms 111.22.160.86
3 2026-08-25 00:35 639232140250307418
1112 ms 111.22.160.86
2 2026-08-25 00:18 639232129927860324
1093 ms 111.22.160.86
1 2026-08-25 00:01 639232119551972438
1112 ms 111.22.160.86