DNS response history for ns2.muneescrackers.com

ns2.muneescrackers.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-26. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 287 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.muneescrackers.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

287 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

62.72.43.95

Most recently resolved hosting IP on selected date

Successful Responses

27

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.muneescrackers.com

Showing DNS history for 2026-08-26 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
27 2026-08-26 08:44 639233297961740122
236 ms 62.72.43.95
26 2026-08-26 08:26 639233287487159094
235 ms 62.72.43.95
25 2026-08-26 08:09 639233276995531707
245 ms 62.72.43.95
24 2026-08-26 07:51 639233266521568229
349 ms 62.72.43.95
23 2026-08-26 07:34 639233256081047431
234 ms 62.72.43.95
22 2026-08-26 06:40 639233223620132921
242 ms 62.72.43.95
21 2026-08-26 06:22 639233213287814244
235 ms 62.72.43.95
20 2026-08-26 06:05 639233202925983161
228 ms 62.72.43.95
19 2026-08-26 05:48 639233192644780696
227 ms 62.72.43.95
18 2026-08-26 05:31 639233182401183833
237 ms 62.72.43.95
17 2026-08-26 05:14 639233172074181051
234 ms 62.72.43.95
16 2026-08-26 04:56 639233161808421455
235 ms 62.72.43.95
15 2026-08-26 04:39 639233151357344052
235 ms 62.72.43.95
14 2026-08-26 04:22 639233141034116946
242 ms 62.72.43.95
13 2026-08-26 04:05 639233130828334142
252 ms 62.72.43.95
12 2026-08-26 03:48 639233120373450007
247 ms 62.72.43.95
11 2026-08-26 03:30 639233110066216193
263 ms 62.72.43.95
10 2026-08-26 02:37 639233078065410564
3 ms 62.72.43.95
9 2026-08-26 02:20 639233067787457832
238 ms 62.72.43.95
8 2026-08-26 02:03 639233057501801162
2134 ms 62.72.43.95
7 2026-08-26 01:46 639233047089431703
3 ms 62.72.43.95
6 2026-08-26 01:28 639233036754790688
2 ms 62.72.43.95
5 2026-08-26 01:11 639233026412602472
242 ms 62.72.43.95
4 2026-08-26 00:54 639233016064066127
240 ms 62.72.43.95
3 2026-08-26 00:37 639233005922655772
236 ms 62.72.43.95
2 2026-08-26 00:20 639232995672256907
239 ms 62.72.43.95
1 2026-08-26 00:02 639232985300872416
244 ms 62.72.43.95