DNS response history for ns2.howdycode.com

ns2.howdycode.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 36 DNS check records, 30 successful responses, 6 failed responses, and 2052 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.howdycode.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

2052 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

70.39.248.204

Most recently resolved hosting IP on selected date

Successful Responses

30

Checks that returned a measurable response

Failed Responses

6

Checks with no response or no returned latency

Failure Rate

17%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.howdycode.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
36 2026-08-27 11:19 639234253963286387
233 ms 70.39.248.204
35 2026-08-27 11:02 639234243654907465
232 ms 70.39.248.204
34 2026-08-27 10:44 639234233269654413
239 ms 70.39.248.204
33 2026-08-27 10:27 639234222943951923
234 ms 70.39.248.204
32 2026-08-27 10:10 639234212558002823
234 ms 70.39.248.204
31 2026-08-27 09:53 639234202117531850
240 ms 70.39.248.204
30 2026-08-27 09:35 639234191649612722
234 ms 70.39.248.204
29 2026-08-27 09:18 639234181105879568
238 ms 70.39.248.204
28 2026-08-27 09:00 639234170713214496
243 ms 70.39.248.204
27 2026-08-27 08:43 639234160341037652
238 ms 70.39.248.204
26 2026-08-27 08:26 639234149799404224
242 ms 70.39.248.204
25 2026-08-27 08:08 639234139553286469
237 ms 70.39.248.204
24 2026-08-27 07:14 639234107183588293
234 ms 70.39.248.204
23 2026-08-27 06:57 639234096905435724
238 ms 70.39.248.204
22 2026-08-27 06:40 639234086579410775
232 ms 70.39.248.204
21 2026-08-27 06:23 639234076291157956
232 ms 70.39.248.204
20 2026-08-27 06:06 639234065981939454
4126 ms 70.39.248.204
19 2026-08-27 05:48 639234055548642997
5126 ms 70.39.248.204
18 2026-08-27 05:31 639234045267979603
4125 ms 70.39.248.204
17 2026-08-27 05:14 639234034999717463
5128 ms 70.39.248.204
16 2026-08-27 04:57 639234024739225358
4125 ms 70.39.248.204
15 2026-08-27 04:40 639234014311170162
2124 ms 70.39.248.204
14 2026-08-27 04:22 639234003806017640
4126 ms 70.39.248.204
13 2026-08-27 04:05 639233993356203030
2129 ms 70.39.248.204
12 2026-08-27 03:11 639233961301716608
-
11 2026-08-27 02:54 639233950834200647
5124 ms 70.39.248.204
10 2026-08-27 02:36 639233940431849026
4125 ms 70.39.248.204
9 2026-08-27 02:19 639233930110596398
5125 ms 70.39.248.204
8 2026-08-27 02:02 639233919705434540
4126 ms 70.39.248.204
7 2026-08-27 01:45 639233909452807845
-
6 2026-08-27 01:27 639233899096420820
4138 ms 70.39.248.204
5 2026-08-27 01:10 639233888707824939
-
4 2026-08-27 00:53 639233878461203802
-
3 2026-08-27 00:36 639233868060868209
-
2 2026-08-27 00:18 639233857450922991
4126 ms 70.39.248.204
1 2026-08-27 00:01 639233846871926285
-