DNS response history for ns.110ken.com

ns.110ken.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 472 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.110ken.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

472 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

182.50.105.55

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 ns.110ken.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:59 639232587225721862
497 ms 182.50.105.55
36 2026-08-25 12:42 639232576780683689
520 ms 182.50.105.55
35 2026-08-25 12:24 639232566381512620
530 ms 182.50.105.55
34 2026-08-25 12:07 639232556111768563
510 ms 182.50.105.55
33 2026-08-25 11:50 639232545839529039
506 ms 182.50.105.55
32 2026-08-25 11:33 639232535349285207
526 ms 182.50.105.55
31 2026-08-25 11:15 639232524938080723
513 ms 182.50.105.55
30 2026-08-25 10:21 639232492740373468
505 ms 182.50.105.55
29 2026-08-25 10:04 639232482235303141
504 ms 182.50.105.55
28 2026-08-25 09:47 639232471861770303
502 ms 182.50.105.55
27 2026-08-25 09:29 639232461630217327
520 ms 182.50.105.55
26 2026-08-25 09:12 639232451282965990
515 ms 182.50.105.55
25 2026-08-25 08:55 639232440814614938
485 ms 182.50.105.55
24 2026-08-25 08:38 639232430410720425
478 ms 182.50.105.55
23 2026-08-25 08:20 639232420003096185
502 ms 182.50.105.55
22 2026-08-25 08:03 639232409467287444
508 ms 182.50.105.55
21 2026-08-25 07:45 639232399077195997
764 ms 182.50.105.55
20 2026-08-25 07:28 639232388731528337
510 ms 182.50.105.55
19 2026-08-25 07:11 639232378288598612
498 ms 182.50.105.55
18 2026-08-25 06:17 639232346196373643
509 ms 182.50.105.55
17 2026-08-25 06:00 639232336112370741
3 ms 182.50.105.55
16 2026-08-25 05:43 639232326146508970
538 ms 182.50.105.55
15 2026-08-25 05:27 639232316189381720
507 ms 182.50.105.55
14 2026-08-25 05:10 639232306217998913
525 ms 182.50.105.55
13 2026-08-25 04:54 639232296255744174
499 ms 182.50.105.55
12 2026-08-25 04:37 639232286095760789
491 ms 182.50.105.55
11 2026-08-25 04:20 639232276086186273
3 ms 182.50.105.55
10 2026-08-25 04:03 639232265900986425
528 ms 182.50.105.55
9 2026-08-25 03:46 639232255723518075
494 ms 182.50.105.55
8 2026-08-25 03:29 639232245484452890
508 ms 182.50.105.55
7 2026-08-25 03:12 639232235157175331
482 ms 182.50.105.55
6 2026-08-25 02:19 639232203197189095
3 ms 182.50.105.55
5 2026-08-25 02:02 639232192844564298
517 ms 182.50.105.55
4 2026-08-25 01:44 639232182496008942
500 ms 182.50.105.55
3 2026-08-25 01:27 639232172197053132
485 ms 182.50.105.55
2 2026-08-25 00:34 639232140250307418
507 ms 182.50.105.55
1 2026-08-25 00:17 639232129927860324
488 ms 182.50.105.55