DNS response history for ns2.dblt.org

ns2.dblt.org 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 35 DNS check records, 35 successful responses, 0 failed responses, and 540 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.dblt.org.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

540 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.74.67.178

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 ns2.dblt.org

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
35 2026-08-25 12:22 639232566381512620
362 ms 209.74.67.178
34 2026-08-25 12:05 639232556111768563
4353 ms 209.74.67.178
33 2026-08-25 11:48 639232545839529039
370 ms 209.74.67.178
32 2026-08-25 11:31 639232535349285207
358 ms 209.74.67.178
31 2026-08-25 11:13 639232524938080723
171 ms 209.74.67.178
30 2026-08-25 10:20 639232492740373468
183 ms 209.74.67.178
29 2026-08-25 10:02 639232482235303141
194 ms 209.74.67.178
28 2026-08-25 09:45 639232471861770303
367 ms 209.74.67.178
27 2026-08-25 09:28 639232461630217327
177 ms 209.74.67.178
26 2026-08-25 09:11 639232451282965990
373 ms 209.74.67.178
25 2026-08-25 08:53 639232440814614938
623 ms 209.74.67.178
24 2026-08-25 08:36 639232430410720425
345 ms 209.74.67.178
23 2026-08-25 08:19 639232420003096185
367 ms 209.74.67.178
22 2026-08-25 08:01 639232409467287444
598 ms 209.74.67.178
21 2026-08-25 07:44 639232399077195997
371 ms 209.74.67.178
20 2026-08-25 07:26 639232388731528337
2310 ms 209.74.67.178
19 2026-08-25 07:09 639232378288598612
360 ms 209.74.67.178
18 2026-08-25 06:15 639232346196373643
632 ms 209.74.67.178
17 2026-08-25 05:58 639232336112370741
462 ms 209.74.67.178
16 2026-08-25 05:42 639232326146508970
366 ms 209.74.67.178
15 2026-08-25 05:25 639232316189381720
265 ms 209.74.67.178
14 2026-08-25 05:09 639232306217998913
195 ms 209.74.67.178
13 2026-08-25 04:52 639232296255744174
3 ms 209.74.67.178
12 2026-08-25 04:35 639232286095760789
349 ms 209.74.67.178
11 2026-08-25 04:18 639232276086186273
183 ms 209.74.67.178
10 2026-08-25 04:02 639232265900986425
341 ms 209.74.67.178
9 2026-08-25 03:45 639232255723518075
7 ms 209.74.67.178
8 2026-08-25 03:28 639232245484452890
344 ms 209.74.67.178
7 2026-08-25 03:10 639232235157175331
446 ms 209.74.67.178
6 2026-08-25 02:17 639232203197189095
356 ms 209.74.67.178
5 2026-08-25 02:00 639232192844564298
345 ms 209.74.67.178
4 2026-08-25 01:43 639232182496008942
13 ms 209.74.67.178
3 2026-08-25 01:25 639232172197053132
2174 ms 209.74.67.178
2 2026-08-25 00:32 639232140250307418
164 ms 209.74.67.178
1 2026-08-25 00:15 639232129927860324
360 ms 209.74.67.178