DNS response history for ns2.playonhonor.com

ns2.playonhonor.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 32 DNS check records, 32 successful responses, 0 failed responses, and 437 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.playonhonor.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

437 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

34.101.177.113

Most recently resolved hosting IP on selected date

Successful Responses

32

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.playonhonor.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
32 2026-08-25 11:30 639232535349285207
318 ms 34.101.177.113
31 2026-08-25 11:13 639232524938080723
158 ms 34.101.177.113
30 2026-08-25 10:19 639232492740373468
2265 ms 34.101.177.113
29 2026-08-25 10:02 639232482235303141
194 ms 34.101.177.113
28 2026-08-25 09:45 639232471861770303
168 ms 34.101.177.113
27 2026-08-25 09:27 639232461630217327
160 ms 34.101.177.113
26 2026-08-25 09:10 639232451282965990
166 ms 34.101.177.113
25 2026-08-25 08:53 639232440814614938
323 ms 34.101.177.113
24 2026-08-25 08:36 639232430410720425
314 ms 34.101.177.113
23 2026-08-25 08:18 639232420003096185
170 ms 34.101.177.113
22 2026-08-25 08:01 639232409467287444
323 ms 34.101.177.113
21 2026-08-25 07:43 639232399077195997
324 ms 34.101.177.113
20 2026-08-25 07:26 639232388731528337
165 ms 34.101.177.113
19 2026-08-25 07:09 639232378288598612
316 ms 34.101.177.113
18 2026-08-25 06:15 639232346196373643
316 ms 34.101.177.113
17 2026-08-25 05:58 639232336112370741
313 ms 34.101.177.113
16 2026-08-25 05:41 639232326146508970
321 ms 34.101.177.113
15 2026-08-25 05:25 639232316189381720
329 ms 34.101.177.113
14 2026-08-25 05:08 639232306217998913
158 ms 34.101.177.113
13 2026-08-25 04:52 639232296255744174
316 ms 34.101.177.113
12 2026-08-25 04:35 639232286095760789
318 ms 34.101.177.113
11 2026-08-25 04:18 639232276086186273
165 ms 34.101.177.113
10 2026-08-25 04:01 639232265900986425
2186 ms 34.101.177.113
9 2026-08-25 03:44 639232255723518075
2261 ms 34.101.177.113
8 2026-08-25 03:27 639232245484452890
315 ms 34.101.177.113
7 2026-08-25 03:10 639232235157175331
173 ms 34.101.177.113
6 2026-08-25 02:17 639232203197189095
319 ms 34.101.177.113
5 2026-08-25 02:00 639232192844564298
159 ms 34.101.177.113
4 2026-08-25 01:42 639232182496008942
156 ms 34.101.177.113
3 2026-08-25 01:25 639232172197053132
323 ms 34.101.177.113
2 2026-08-25 00:32 639232140250307418
320 ms 34.101.177.113
1 2026-08-25 00:15 639232129927860324
157 ms 34.101.177.113