DNS response history for ns2.blisfulpath.com

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

27

Historical checks stored for this nameserver on selected date

Average Latency

549 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 08:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

45.83.251.16

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

Showing DNS history for 2026-08-30 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-30 08:37 639236755602384085
15 ms 45.83.251.16
26 2026-08-30 08:20 639236745600094925
42 ms 45.83.251.16
25 2026-08-30 08:03 639236735311262753
43 ms 45.83.251.16
24 2026-08-30 07:46 639236724996745235
9 ms 45.83.251.16
23 2026-08-30 07:29 639236714839899761
9 ms 45.83.251.16
22 2026-08-30 07:12 639236704748431488
14 ms 45.83.251.16
21 2026-08-30 06:55 639236694430128550
4033 ms 45.83.251.16
20 2026-08-30 06:37 639236684143292417
2030 ms 45.83.251.16
19 2026-08-30 06:20 639236673972499943
4 ms 45.83.251.16
18 2026-08-30 05:27 639236642126522802
2026 ms 45.83.251.16
17 2026-08-30 05:11 639236632183518198
34 ms 45.83.251.16
16 2026-08-30 04:54 639236622289312589
2028 ms 45.83.251.16
15 2026-08-30 04:38 639236612490676525
48 ms 45.83.251.16
14 2026-08-30 04:21 639236602582494852
7 ms 45.83.251.16
13 2026-08-30 04:05 639236592511706469
90 ms 45.83.251.16
12 2026-08-30 03:48 639236582441006869
33 ms 45.83.251.16
11 2026-08-30 03:31 639236572478785089
24 ms 45.83.251.16
10 2026-08-30 03:15 639236562556749999
13 ms 45.83.251.16
9 2026-08-30 02:58 639236552353482281
2054 ms 45.83.251.16
8 2026-08-30 02:41 639236542188881607
2065 ms 45.83.251.16
7 2026-08-30 02:24 639236531885440105
6 ms 45.83.251.16
6 2026-08-30 01:30 639236499922985383
22 ms 45.83.251.16
5 2026-08-30 01:13 639236489713594431
32 ms 45.83.251.16
4 2026-08-30 00:57 639236479750443901
72 ms 45.83.251.16
3 2026-08-30 00:40 639236469719936375
5 ms 45.83.251.16
2 2026-08-30 00:23 639236459579244885
34 ms 45.83.251.16
1 2026-08-30 00:06 639236449582837549
30 ms 45.83.251.16