DNS response history for ns5.bloodymonster.com

ns5.bloodymonster.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-24. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 547 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 ns5.bloodymonster.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

547 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.28.106.86

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 ns5.bloodymonster.com

Showing DNS history for 2026-08-24 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-24 14:06 639231765923559455
157 ms 50.28.106.86
33 2026-08-24 13:50 639231755868832964
310 ms 50.28.106.86
32 2026-08-24 13:33 639231745628278877
2171 ms 50.28.106.86
31 2026-08-24 13:15 639231735407682062
2157 ms 50.28.106.86
30 2026-08-24 12:23 639231703815441688
301 ms 50.28.106.86
29 2026-08-24 12:06 639231693747052549
307 ms 50.28.106.86
28 2026-08-24 11:49 639231683712487276
10 ms 50.28.106.86
27 2026-08-24 11:32 639231673513573868
304 ms 50.28.106.86
26 2026-08-24 10:39 639231641791249939
355 ms 50.28.106.86
25 2026-08-24 10:23 639231631866211033
295 ms 50.28.106.86
24 2026-08-24 10:06 639231621644955316
310 ms 50.28.106.86
23 2026-08-24 09:49 639231611478799259
307 ms 50.28.106.86
22 2026-08-24 08:56 639231579923718211
302 ms 50.28.106.86
21 2026-08-24 08:40 639231569810702936
2163 ms 50.28.106.86
20 2026-08-24 08:22 639231559762411619
172 ms 50.28.106.86
19 2026-08-24 08:06 639231549663595407
418 ms 50.28.106.86
18 2026-08-24 07:13 639231518076817246
310 ms 50.28.106.86
17 2026-08-24 06:57 639231508078650885
3 ms 50.28.106.86
16 2026-08-24 06:40 639231498210697093
4 ms 50.28.106.86
15 2026-08-24 06:23 639231488109699360
318 ms 50.28.106.86
14 2026-08-24 05:31 639231456772510692
161 ms 50.28.106.86
13 2026-08-24 05:15 639231447084631185
2292 ms 50.28.106.86
12 2026-08-24 04:58 639231437208519473
296 ms 50.28.106.86
11 2026-08-24 04:42 639231427209627490
32 ms 50.28.106.86
10 2026-08-24 03:49 639231395791246644
4005 ms 50.28.106.86
9 2026-08-24 03:33 639231386075551458
311 ms 50.28.106.86
8 2026-08-24 03:17 639231376208713791
151 ms 50.28.106.86
7 2026-08-24 03:00 639231366170589276
7 ms 50.28.106.86
6 2026-08-24 02:08 639231334732159368
3 ms 50.28.106.86
5 2026-08-24 01:51 639231325035670078
3 ms 50.28.106.86
4 2026-08-24 01:35 639231315132253837
157 ms 50.28.106.86
3 2026-08-24 01:18 639231305014280808
300 ms 50.28.106.86
2 2026-08-24 00:26 639231273779380675
174 ms 50.28.106.86
1 2026-08-24 00:10 639231264180839154
35 ms 50.28.106.86