DNS response history for ns1.s33d.blog

ns1.s33d.blog 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-25. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 230 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.s33d.blog.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

230 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.114.28.3

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 ns1.s33d.blog

Showing DNS history for 2026-08-25 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-25 11:59 639232556111768563
38 ms 212.114.28.3
33 2026-08-25 11:42 639232545839529039
61 ms 212.114.28.3
32 2026-08-25 11:25 639232535349285207
59 ms 212.114.28.3
31 2026-08-25 11:07 639232524938080723
71 ms 212.114.28.3
30 2026-08-25 10:13 639232492740373468
25 ms 212.114.28.3
29 2026-08-25 09:56 639232482235303141
155 ms 212.114.28.3
28 2026-08-25 09:39 639232471861770303
37 ms 212.114.28.3
27 2026-08-25 09:22 639232461630217327
94 ms 212.114.28.3
26 2026-08-25 09:04 639232451282965990
37 ms 212.114.28.3
25 2026-08-25 08:47 639232440814614938
65 ms 212.114.28.3
24 2026-08-25 08:30 639232430410720425
49 ms 212.114.28.3
23 2026-08-25 08:12 639232420003096185
73 ms 212.114.28.3
22 2026-08-25 07:55 639232409467287444
41 ms 212.114.28.3
21 2026-08-25 07:37 639232399077195997
72 ms 212.114.28.3
20 2026-08-25 07:20 639232388731528337
2044 ms 212.114.28.3
19 2026-08-25 07:03 639232378288598612
45 ms 212.114.28.3
18 2026-08-25 06:09 639232346196373643
27 ms 212.114.28.3
17 2026-08-25 05:52 639232336112370741
46 ms 212.114.28.3
16 2026-08-25 05:36 639232326146508970
32 ms 212.114.28.3
15 2026-08-25 05:19 639232316189381720
68 ms 212.114.28.3
14 2026-08-25 05:03 639232306217998913
53 ms 212.114.28.3
13 2026-08-25 04:46 639232296255744174
64 ms 212.114.28.3
12 2026-08-25 04:29 639232286095760789
88 ms 212.114.28.3
11 2026-08-25 04:12 639232276086186273
91 ms 212.114.28.3
10 2026-08-25 03:55 639232265900986425
40 ms 212.114.28.3
9 2026-08-25 03:38 639232255723518075
55 ms 212.114.28.3
8 2026-08-25 03:21 639232245484452890
39 ms 212.114.28.3
7 2026-08-25 03:04 639232235157175331
2033 ms 212.114.28.3
6 2026-08-25 02:11 639232203197189095
38 ms 212.114.28.3
5 2026-08-25 01:54 639232192844564298
44 ms 212.114.28.3
4 2026-08-25 01:36 639232182496008942
2047 ms 212.114.28.3
3 2026-08-25 01:19 639232172197053132
20 ms 212.114.28.3
2 2026-08-25 00:26 639232140250307418
45 ms 212.114.28.3
1 2026-08-25 00:09 639232129927860324
27 ms 212.114.28.3