DNS response history for ns1.chainsblogging.com

ns1.chainsblogging.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 35 DNS check records, 35 successful responses, 0 failed responses, and 219 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 ns1.chainsblogging.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

219 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

87.98.241.218

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns1.chainsblogging.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
35 2026-08-26 11:46 639233414056832719
85 ms 87.98.241.218
34 2026-08-26 11:28 639233403515141099
57 ms 87.98.241.218
33 2026-08-26 10:34 639233370841350248
45 ms 87.98.241.218
32 2026-08-26 10:16 639233360361507238
2033 ms 87.98.241.218
31 2026-08-26 09:59 639233350067824371
18 ms 87.98.241.218
30 2026-08-26 09:42 639233339545274518
36 ms 87.98.241.218
29 2026-08-26 09:24 639233329214918079
38 ms 87.98.241.218
28 2026-08-26 09:07 639233318749762337
68 ms 87.98.241.218
27 2026-08-26 08:50 639233308387917838
20 ms 87.98.241.218
26 2026-08-26 08:32 639233297961740122
56 ms 87.98.241.218
25 2026-08-26 08:15 639233287487159094
53 ms 87.98.241.218
24 2026-08-26 07:57 639233276995531707
36 ms 87.98.241.218
23 2026-08-26 07:40 639233266521568229
65 ms 87.98.241.218
22 2026-08-26 07:22 639233256081047431
35 ms 87.98.241.218
21 2026-08-26 06:28 639233223620132921
36 ms 87.98.241.218
20 2026-08-26 06:11 639233213287814244
53 ms 87.98.241.218
19 2026-08-26 05:54 639233202925983161
37 ms 87.98.241.218
18 2026-08-26 05:37 639233192644780696
58 ms 87.98.241.218
17 2026-08-26 05:20 639233182401183833
43 ms 87.98.241.218
16 2026-08-26 05:03 639233172074181051
33 ms 87.98.241.218
15 2026-08-26 04:45 639233161808421455
34 ms 87.98.241.218
14 2026-08-26 04:28 639233151357344052
56 ms 87.98.241.218
13 2026-08-26 04:11 639233141034116946
73 ms 87.98.241.218
12 2026-08-26 03:54 639233130828334142
66 ms 87.98.241.218
11 2026-08-26 03:36 639233120373450007
50 ms 87.98.241.218
10 2026-08-26 03:19 639233110066216193
44 ms 87.98.241.218
9 2026-08-26 02:26 639233078065410564
4052 ms 87.98.241.218
8 2026-08-26 02:09 639233067787457832
33 ms 87.98.241.218
7 2026-08-26 01:52 639233057501801162
33 ms 87.98.241.218
6 2026-08-26 01:34 639233047089431703
32 ms 87.98.241.218
5 2026-08-26 01:17 639233036754790688
43 ms 87.98.241.218
4 2026-08-26 01:00 639233026412602472
37 ms 87.98.241.218
3 2026-08-26 00:42 639233016064066127
36 ms 87.98.241.218
2 2026-08-26 00:25 639233005922655772
112 ms 87.98.241.218
1 2026-08-26 00:08 639232995672256907
54 ms 87.98.241.218