DNS response history for ns2.cre9.com

ns2.cre9.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 33 DNS check records, 31 successful responses, 2 failed responses, and 535 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.cre9.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

535 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.96.161.144

Most recently resolved hosting IP on selected date

Successful Responses

31

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

6%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.cre9.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
33 2026-08-25 11:33 639232535349285207
10 ms 66.96.161.144
32 2026-08-25 11:15 639232524938080723
249 ms 66.96.161.144
31 2026-08-25 10:22 639232492740373468
3 ms 66.96.161.144
30 2026-08-25 10:05 639232482235303141
243 ms 66.96.161.144
29 2026-08-25 09:47 639232471861770303
11 ms 66.96.161.144
28 2026-08-25 09:30 639232461630217327
127 ms 66.96.161.144
27 2026-08-25 09:13 639232451282965990
1291 ms 66.96.161.144
26 2026-08-25 08:55 639232440814614938
1793 ms 66.96.161.144
25 2026-08-25 08:38 639232430410720425
6 ms 66.96.161.144
24 2026-08-25 08:21 639232420003096185
4 ms 66.96.161.144
23 2026-08-25 08:03 639232409467287444
4048 ms 66.96.161.144
22 2026-08-25 07:46 639232399077195997
1039 ms 66.96.161.144
21 2026-08-25 07:28 639232388731528337
-
20 2026-08-25 07:11 639232378288598612
-
19 2026-08-25 06:17 639232346196373643
11 ms 66.96.161.144
18 2026-08-25 06:00 639232336112370741
299 ms 66.96.161.144
17 2026-08-25 05:44 639232326146508970
3665 ms 66.96.161.144
16 2026-08-25 05:27 639232316189381720
159 ms 66.96.161.144
15 2026-08-25 05:11 639232306217998913
4 ms 66.96.161.144
14 2026-08-25 04:54 639232296255744174
126 ms 66.96.161.144
13 2026-08-25 04:37 639232286095760789
171 ms 66.96.161.144
12 2026-08-25 04:20 639232276086186273
237 ms 66.96.161.144
11 2026-08-25 04:04 639232265900986425
3 ms 66.96.161.144
10 2026-08-25 03:47 639232255723518075
154 ms 66.96.161.144
9 2026-08-25 03:30 639232245484452890
218 ms 66.96.161.144
8 2026-08-25 03:12 639232235157175331
1638 ms 66.96.161.144
7 2026-08-25 02:19 639232203197189095
123 ms 66.96.161.144
6 2026-08-25 02:02 639232192844564298
125 ms 66.96.161.144
5 2026-08-25 01:45 639232182496008942
123 ms 66.96.161.144
4 2026-08-25 01:27 639232172197053132
264 ms 66.96.161.144
3 2026-08-25 00:34 639232140250307418
159 ms 66.96.161.144
2 2026-08-25 00:17 639232129927860324
127 ms 66.96.161.144
1 2026-08-25 00:00 639232119551972438
158 ms 66.96.161.144