DNS response history for ns.39ch.net

ns.39ch.net 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 38 DNS check records, 38 successful responses, 0 failed responses, and 715 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 ns.39ch.net.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

715 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.206.118.58

Most recently resolved hosting IP on selected date

Successful Responses

38

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 ns.39ch.net

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
38 2026-08-25 13:00 639232587225721862
877 ms 61.206.118.58
37 2026-08-25 12:42 639232576780683689
866 ms 61.206.118.58
36 2026-08-25 12:25 639232566381512620
963 ms 61.206.118.58
35 2026-08-25 12:08 639232556111768563
715 ms 61.206.118.58
34 2026-08-25 11:50 639232545839529039
786 ms 61.206.118.58
33 2026-08-25 11:33 639232535349285207
711 ms 61.206.118.58
32 2026-08-25 11:16 639232524938080723
776 ms 61.206.118.58
31 2026-08-25 10:22 639232492740373468
710 ms 61.206.118.58
30 2026-08-25 10:05 639232482235303141
814 ms 61.206.118.58
29 2026-08-25 09:47 639232471861770303
703 ms 61.206.118.58
28 2026-08-25 09:30 639232461630217327
725 ms 61.206.118.58
27 2026-08-25 09:13 639232451282965990
709 ms 61.206.118.58
26 2026-08-25 08:56 639232440814614938
751 ms 61.206.118.58
25 2026-08-25 08:38 639232430410720425
714 ms 61.206.118.58
24 2026-08-25 08:21 639232420003096185
710 ms 61.206.118.58
23 2026-08-25 08:03 639232409467287444
701 ms 61.206.118.58
22 2026-08-25 07:46 639232399077195997
699 ms 61.206.118.58
21 2026-08-25 07:29 639232388731528337
772 ms 61.206.118.58
20 2026-08-25 07:11 639232378288598612
696 ms 61.206.118.58
19 2026-08-25 06:17 639232346196373643
693 ms 61.206.118.58
18 2026-08-25 06:01 639232336112370741
696 ms 61.206.118.58
17 2026-08-25 05:44 639232326146508970
693 ms 61.206.118.58
16 2026-08-25 05:27 639232316189381720
711 ms 61.206.118.58
15 2026-08-25 05:11 639232306217998913
711 ms 61.206.118.58
14 2026-08-25 04:54 639232296255744174
690 ms 61.206.118.58
13 2026-08-25 04:37 639232286095760789
711 ms 61.206.118.58
12 2026-08-25 04:20 639232276086186273
3 ms 61.206.118.58
11 2026-08-25 04:04 639232265900986425
697 ms 61.206.118.58
10 2026-08-25 03:47 639232255723518075
693 ms 61.206.118.58
9 2026-08-25 03:30 639232245484452890
686 ms 61.206.118.58
8 2026-08-25 03:13 639232235157175331
704 ms 61.206.118.58
7 2026-08-25 02:19 639232203197189095
692 ms 61.206.118.58
6 2026-08-25 02:02 639232192844564298
686 ms 61.206.118.58
5 2026-08-25 01:45 639232182496008942
697 ms 61.206.118.58
4 2026-08-25 01:28 639232172197053132
953 ms 61.206.118.58
3 2026-08-25 00:34 639232140250307418
691 ms 61.206.118.58
2 2026-08-25 00:17 639232129927860324
693 ms 61.206.118.58
1 2026-08-25 00:00 639232119551972438
686 ms 61.206.118.58