DNS response history for ns2.bloodymonster.com

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

38

Historical checks stored for this nameserver on selected date

Average Latency

563 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:43

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

38

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

Showing DNS history for 2026-08-27 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
38 2026-08-27 12:43 639234307007468133
2210 ms 50.28.106.86
37 2026-08-27 12:26 639234296664302575
156 ms 50.28.106.86
36 2026-08-27 12:08 639234286253196126
157 ms 50.28.106.86
35 2026-08-27 11:15 639234253963286387
159 ms 50.28.106.86
34 2026-08-27 10:58 639234243654907465
156 ms 50.28.106.86
33 2026-08-27 10:40 639234233269654413
295 ms 50.28.106.86
32 2026-08-27 10:23 639234222943951923
2196 ms 50.28.106.86
31 2026-08-27 10:06 639234212558002823
309 ms 50.28.106.86
30 2026-08-27 09:48 639234202117531850
301 ms 50.28.106.86
29 2026-08-27 09:31 639234191649612722
302 ms 50.28.106.86
28 2026-08-27 09:13 639234181105879568
308 ms 50.28.106.86
27 2026-08-27 08:56 639234170713214496
2165 ms 50.28.106.86
26 2026-08-27 08:39 639234160341037652
148 ms 50.28.106.86
25 2026-08-27 08:21 639234149799404224
303 ms 50.28.106.86
24 2026-08-27 08:03 639234139553286469
295 ms 50.28.106.86
23 2026-08-27 07:10 639234107183588293
158 ms 50.28.106.86
22 2026-08-27 06:53 639234096905435724
4 ms 50.28.106.86
21 2026-08-27 06:36 639234086579410775
155 ms 50.28.106.86
20 2026-08-27 06:18 639234076291157956
156 ms 50.28.106.86
19 2026-08-27 06:01 639234065981939454
301 ms 50.28.106.86
18 2026-08-27 05:44 639234055548642997
149 ms 50.28.106.86
17 2026-08-27 05:27 639234045267979603
164 ms 50.28.106.86
16 2026-08-27 05:10 639234034999717463
156 ms 50.28.106.86
15 2026-08-27 04:53 639234024739225358
155 ms 50.28.106.86
14 2026-08-27 04:35 639234014311170162
147 ms 50.28.106.86
13 2026-08-27 04:18 639234003806017640
159 ms 50.28.106.86
12 2026-08-27 04:00 639233993356203030
2199 ms 50.28.106.86
11 2026-08-27 03:07 639233961301716608
148 ms 50.28.106.86
10 2026-08-27 02:50 639233950834200647
2168 ms 50.28.106.86
9 2026-08-27 02:32 639233940431849026
2165 ms 50.28.106.86
8 2026-08-27 02:15 639233930110596398
7 ms 50.28.106.86
7 2026-08-27 01:58 639233919705434540
155 ms 50.28.106.86
6 2026-08-27 01:41 639233909452807845
2174 ms 50.28.106.86
5 2026-08-27 01:23 639233899096420820
314 ms 50.28.106.86
4 2026-08-27 01:06 639233888707824939
302 ms 50.28.106.86
3 2026-08-27 00:49 639233878461203802
148 ms 50.28.106.86
2 2026-08-27 00:32 639233868060868209
302 ms 50.28.106.86
1 2026-08-27 00:14 639233857450922991
148 ms 50.28.106.86