DNS response history for ns.timesensor.com

ns.timesensor.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 35 DNS check records, 35 successful responses, 0 failed responses, and 273 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.timesensor.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

273 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.116.108.103

Most recently resolved hosting IP on selected date

Successful Responses

35

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.timesensor.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
35 2026-08-27 11:05 639234253963286387
7 ms 66.116.108.103
34 2026-08-27 10:47 639234243654907465
25 ms 66.116.108.103
33 2026-08-27 10:30 639234233269654413
65 ms 66.116.108.103
32 2026-08-27 10:13 639234222943951923
5 ms 66.116.108.103
31 2026-08-27 09:56 639234212558002823
10 ms 66.116.108.103
30 2026-08-27 09:38 639234202117531850
56 ms 66.116.108.103
29 2026-08-27 09:21 639234191649612722
5 ms 66.116.108.103
28 2026-08-27 09:03 639234181105879568
14 ms 66.116.108.103
27 2026-08-27 08:46 639234170713214496
30 ms 66.116.108.103
26 2026-08-27 08:29 639234160341037652
14 ms 66.116.108.103
25 2026-08-27 08:11 639234149799404224
83 ms 66.116.108.103
24 2026-08-27 07:54 639234139553286469
2095 ms 66.116.108.103
23 2026-08-27 07:00 639234107183588293
5 ms 66.116.108.103
22 2026-08-27 06:43 639234096905435724
100 ms 66.116.108.103
21 2026-08-27 06:26 639234086579410775
15 ms 66.116.108.103
20 2026-08-27 06:09 639234076291157956
30 ms 66.116.108.103
19 2026-08-27 05:51 639234065981939454
2044 ms 66.116.108.103
18 2026-08-27 05:34 639234055548642997
8 ms 66.116.108.103
17 2026-08-27 05:17 639234045267979603
4 ms 66.116.108.103
16 2026-08-27 05:00 639234034999717463
12 ms 66.116.108.103
15 2026-08-27 04:43 639234024739225358
67 ms 66.116.108.103
14 2026-08-27 04:25 639234014311170162
90 ms 66.116.108.103
13 2026-08-27 04:08 639234003806017640
34 ms 66.116.108.103
12 2026-08-27 03:50 639233993356203030
28 ms 66.116.108.103
11 2026-08-27 02:57 639233961301716608
2123 ms 66.116.108.103
10 2026-08-27 02:40 639233950834200647
101 ms 66.116.108.103
9 2026-08-27 02:22 639233940431849026
53 ms 66.116.108.103
8 2026-08-27 02:05 639233930110596398
2106 ms 66.116.108.103
7 2026-08-27 01:47 639233919705434540
66 ms 66.116.108.103
6 2026-08-27 01:30 639233909452807845
43 ms 66.116.108.103
5 2026-08-27 01:13 639233899096420820
30 ms 66.116.108.103
4 2026-08-27 00:56 639233888707824939
29 ms 66.116.108.103
3 2026-08-27 00:39 639233878461203802
46 ms 66.116.108.103
2 2026-08-27 00:21 639233868060868209
87 ms 66.116.108.103
1 2026-08-27 00:04 639233857450922991
29 ms 66.116.108.103