DNS response history for ns.emilong.com

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

26

Historical checks stored for this nameserver on selected date

Average Latency

324 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 08:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

174.136.110.66

Most recently resolved hosting IP on selected date

Successful Responses

26

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.emilong.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
26 2026-08-27 08:37 639234160341037652
32 ms 174.136.110.66
25 2026-08-27 08:20 639234149799404224
347 ms 174.136.110.66
24 2026-08-27 08:02 639234139553286469
313 ms 174.136.110.66
23 2026-08-27 07:09 639234107183588293
318 ms 174.136.110.66
22 2026-08-27 06:52 639234096905435724
326 ms 174.136.110.66
21 2026-08-27 06:34 639234086579410775
2009 ms 174.136.110.66
20 2026-08-27 06:17 639234076291157956
17 ms 174.136.110.66
19 2026-08-27 06:00 639234065981939454
329 ms 174.136.110.66
18 2026-08-27 05:43 639234055548642997
8 ms 174.136.110.66
17 2026-08-27 05:25 639234045267979603
180 ms 174.136.110.66
16 2026-08-27 05:08 639234034999717463
161 ms 174.136.110.66
15 2026-08-27 04:51 639234024739225358
315 ms 174.136.110.66
14 2026-08-27 04:34 639234014311170162
333 ms 174.136.110.66
13 2026-08-27 04:17 639234003806017640
437 ms 174.136.110.66
12 2026-08-27 03:59 639233993356203030
329 ms 174.136.110.66
11 2026-08-27 03:06 639233961301716608
320 ms 174.136.110.66
10 2026-08-27 02:48 639233950834200647
198 ms 174.136.110.66
9 2026-08-27 02:31 639233940431849026
312 ms 174.136.110.66
8 2026-08-27 02:14 639233930110596398
320 ms 174.136.110.66
7 2026-08-27 01:56 639233919705434540
319 ms 174.136.110.66
6 2026-08-27 01:39 639233909452807845
311 ms 174.136.110.66
5 2026-08-27 01:22 639233899096420820
7 ms 174.136.110.66
4 2026-08-27 01:05 639233888707824939
326 ms 174.136.110.66
3 2026-08-27 00:47 639233878461203802
309 ms 174.136.110.66
2 2026-08-27 00:30 639233868060868209
327 ms 174.136.110.66
1 2026-08-27 00:13 639233857450922991
227 ms 174.136.110.66