DNS response history for ns2.monsterchannelfilmfestival.com

ns2.monsterchannelfilmfestival.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-09-01. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 296 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.monsterchannelfilmfestival.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

296 ms

Calculated from available response records

Latest Check on Selected Date

2026-09-01 12:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

72.167.140.59

Most recently resolved hosting IP on selected date

Successful Responses

37

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

Showing DNS history for 2026-09-01 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
37 2026-09-01 12:45 639238628486902752
9 ms 72.167.140.59
36 2026-09-01 12:28 639238617906743100
351 ms 72.167.140.59
35 2026-09-01 12:10 639238607506044626
360 ms 72.167.140.59
34 2026-09-01 11:53 639238597040761406
353 ms 72.167.140.59
33 2026-09-01 11:35 639238586261546969
361 ms 72.167.140.59
32 2026-09-01 11:17 639238575587642333
356 ms 72.167.140.59
31 2026-09-01 10:23 639238543127398267
336 ms 72.167.140.59
30 2026-09-01 10:06 639238532668234016
5 ms 72.167.140.59
29 2026-09-01 09:48 639238522029321761
16 ms 72.167.140.59
28 2026-09-01 09:30 639238511519050351
8 ms 72.167.140.59
27 2026-09-01 09:13 639238500942239673
346 ms 72.167.140.59
26 2026-09-01 08:55 639238490412377398
9 ms 72.167.140.59
25 2026-09-01 08:37 639238479833203021
339 ms 72.167.140.59
24 2026-09-01 08:20 639238469140507479
3 ms 72.167.140.59
23 2026-09-01 08:02 639238458443560361
343 ms 72.167.140.59
22 2026-09-01 07:44 639238447694851502
349 ms 72.167.140.59
21 2026-09-01 07:26 639238436624109087
346 ms 72.167.140.59
20 2026-09-01 07:07 639238425565611335
347 ms 72.167.140.59
19 2026-09-01 06:12 639238392250222581
348 ms 72.167.140.59
18 2026-09-01 05:54 639238381322537831
335 ms 72.167.140.59
17 2026-09-01 05:35 639238370248186084
337 ms 72.167.140.59
16 2026-09-01 05:17 639238359264687845
348 ms 72.167.140.59
15 2026-09-01 04:59 639238348534621818
341 ms 72.167.140.59
14 2026-09-01 04:41 639238337725739433
338 ms 72.167.140.59
13 2026-09-01 04:23 639238326844749368
338 ms 72.167.140.59
12 2026-09-01 04:04 639238315792024737
357 ms 72.167.140.59
11 2026-09-01 03:46 639238304931064768
354 ms 72.167.140.59
10 2026-09-01 03:28 639238294131483803
367 ms 72.167.140.59
9 2026-09-01 03:10 639238283314985519
362 ms 72.167.140.59
8 2026-09-01 02:52 639238272374093187
354 ms 72.167.140.59
7 2026-09-01 01:58 639238240032549922
367 ms 72.167.140.59
6 2026-09-01 01:40 639238229204177368
358 ms 72.167.140.59
5 2026-09-01 01:22 639238218326150282
363 ms 72.167.140.59
4 2026-09-01 01:04 639238207574700853
367 ms 72.167.140.59
3 2026-09-01 00:46 639238196660283915
356 ms 72.167.140.59
2 2026-09-01 00:28 639238185782358546
351 ms 72.167.140.59
1 2026-09-01 00:10 639238175054391781
361 ms 72.167.140.59