DNS response history for ns2.creomaxserv.com

ns2.creomaxserv.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 34 DNS check records, 34 successful responses, 0 failed responses, and 235 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.creomaxserv.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

235 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

81.91.77.54

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns2.creomaxserv.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
34 2026-08-25 12:05 639232556111768563
113 ms 81.91.77.54
33 2026-08-25 11:48 639232545839529039
106 ms 81.91.77.54
32 2026-08-25 11:30 639232535349285207
214 ms 81.91.77.54
31 2026-08-25 11:13 639232524938080723
230 ms 81.91.77.54
30 2026-08-25 10:19 639232492740373468
13 ms 81.91.77.54
29 2026-08-25 10:02 639232482235303141
110 ms 81.91.77.54
28 2026-08-25 09:44 639232471861770303
215 ms 81.91.77.54
27 2026-08-25 09:27 639232461630217327
217 ms 81.91.77.54
26 2026-08-25 09:10 639232451282965990
214 ms 81.91.77.54
25 2026-08-25 08:53 639232440814614938
108 ms 81.91.77.54
24 2026-08-25 08:35 639232430410720425
213 ms 81.91.77.54
23 2026-08-25 08:18 639232420003096185
214 ms 81.91.77.54
22 2026-08-25 08:01 639232409467287444
108 ms 81.91.77.54
21 2026-08-25 07:43 639232399077195997
221 ms 81.91.77.54
20 2026-08-25 07:26 639232388731528337
222 ms 81.91.77.54
19 2026-08-25 07:08 639232378288598612
2011 ms 81.91.77.54
18 2026-08-25 06:15 639232346196373643
134 ms 81.91.77.54
17 2026-08-25 05:58 639232336112370741
213 ms 81.91.77.54
16 2026-08-25 05:41 639232326146508970
222 ms 81.91.77.54
15 2026-08-25 05:25 639232316189381720
220 ms 81.91.77.54
14 2026-08-25 05:08 639232306217998913
113 ms 81.91.77.54
13 2026-08-25 04:52 639232296255744174
216 ms 81.91.77.54
12 2026-08-25 04:35 639232286095760789
116 ms 81.91.77.54
11 2026-08-25 04:18 639232276086186273
219 ms 81.91.77.54
10 2026-08-25 04:01 639232265900986425
220 ms 81.91.77.54
9 2026-08-25 03:44 639232255723518075
229 ms 81.91.77.54
8 2026-08-25 03:27 639232245484452890
224 ms 81.91.77.54
7 2026-08-25 03:10 639232235157175331
216 ms 81.91.77.54
6 2026-08-25 02:17 639232203197189095
226 ms 81.91.77.54
5 2026-08-25 01:59 639232192844564298
230 ms 81.91.77.54
4 2026-08-25 01:42 639232182496008942
2 ms 81.91.77.54
3 2026-08-25 01:25 639232172197053132
225 ms 81.91.77.54
2 2026-08-25 00:32 639232140250307418
225 ms 81.91.77.54
1 2026-08-25 00:15 639232129927860324
224 ms 81.91.77.54