DNS response history for ns2.crewcierge.com

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

28

Historical checks stored for this nameserver on selected date

Average Latency

528 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

72.167.135.43

Most recently resolved hosting IP on selected date

Successful Responses

28

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.crewcierge.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
28 2026-08-25 09:45 639232471861770303
348 ms 72.167.135.43
27 2026-08-25 09:28 639232461630217327
346 ms 72.167.135.43
26 2026-08-25 09:10 639232451282965990
346 ms 72.167.135.43
25 2026-08-25 08:53 639232440814614938
339 ms 72.167.135.43
24 2026-08-25 08:36 639232430410720425
356 ms 72.167.135.43
23 2026-08-25 08:18 639232420003096185
212 ms 72.167.135.43
22 2026-08-25 08:01 639232409467287444
344 ms 72.167.135.43
21 2026-08-25 07:43 639232399077195997
349 ms 72.167.135.43
20 2026-08-25 07:26 639232388731528337
337 ms 72.167.135.43
19 2026-08-25 07:09 639232378288598612
335 ms 72.167.135.43
18 2026-08-25 06:15 639232346196373643
339 ms 72.167.135.43
17 2026-08-25 05:58 639232336112370741
2176 ms 72.167.135.43
16 2026-08-25 05:42 639232326146508970
2160 ms 72.167.135.43
15 2026-08-25 05:25 639232316189381720
350 ms 72.167.135.43
14 2026-08-25 05:08 639232306217998913
3 ms 72.167.135.43
13 2026-08-25 04:52 639232296255744174
332 ms 72.167.135.43
12 2026-08-25 04:35 639232286095760789
340 ms 72.167.135.43
11 2026-08-25 04:18 639232276086186273
346 ms 72.167.135.43
10 2026-08-25 04:01 639232265900986425
343 ms 72.167.135.43
9 2026-08-25 03:44 639232255723518075
354 ms 72.167.135.43
8 2026-08-25 03:27 639232245484452890
341 ms 72.167.135.43
7 2026-08-25 03:10 639232235157175331
340 ms 72.167.135.43
6 2026-08-25 02:17 639232203197189095
354 ms 72.167.135.43
5 2026-08-25 02:00 639232192844564298
352 ms 72.167.135.43
4 2026-08-25 01:42 639232182496008942
2295 ms 72.167.135.43
3 2026-08-25 01:25 639232172197053132
358 ms 72.167.135.43
2 2026-08-25 00:32 639232140250307418
342 ms 72.167.135.43
1 2026-08-25 00:15 639232129927860324
352 ms 72.167.135.43