DNS response history for ns2.nlpdns.com

ns2.nlpdns.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-24. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 516 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.nlpdns.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

516 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.79.167.108

Most recently resolved hosting IP on selected date

Successful Responses

26

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

Showing DNS history for 2026-08-24 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
26 2026-08-24 10:41 639231641791249939
5 ms 210.79.167.108
25 2026-08-24 10:25 639231631866211033
557 ms 210.79.167.108
24 2026-08-24 10:08 639231621644955316
557 ms 210.79.167.108
23 2026-08-24 09:51 639231611478799259
204 ms 210.79.167.108
22 2026-08-24 08:58 639231579923718211
2190 ms 210.79.167.108
21 2026-08-24 08:42 639231569810702936
409 ms 210.79.167.108
20 2026-08-24 08:25 639231559762411619
2031 ms 210.79.167.108
19 2026-08-24 08:08 639231549663595407
3 ms 210.79.167.108
18 2026-08-24 07:15 639231518076817246
10 ms 210.79.167.108
17 2026-08-24 06:59 639231508078650885
395 ms 210.79.167.108
16 2026-08-24 06:42 639231498210697093
572 ms 210.79.167.108
15 2026-08-24 06:25 639231488109699360
7 ms 210.79.167.108
14 2026-08-24 05:33 639231456772510692
3 ms 210.79.167.108
13 2026-08-24 05:17 639231447084631185
146 ms 210.79.167.108
12 2026-08-24 05:00 639231437208519473
3 ms 210.79.167.108
11 2026-08-24 04:44 639231427209627490
565 ms 210.79.167.108
10 2026-08-24 03:51 639231395791246644
394 ms 210.79.167.108
9 2026-08-24 03:35 639231386075551458
2005 ms 210.79.167.108
8 2026-08-24 03:19 639231376208713791
565 ms 210.79.167.108
7 2026-08-24 03:02 639231366170589276
147 ms 210.79.167.108
6 2026-08-24 02:10 639231334732159368
3 ms 210.79.167.108
5 2026-08-24 01:53 639231325035670078
30 ms 210.79.167.108
4 2026-08-24 01:37 639231315132253837
2007 ms 210.79.167.108
3 2026-08-24 01:20 639231305014280808
3 ms 210.79.167.108
2 2026-08-24 00:28 639231273779380675
199 ms 210.79.167.108
1 2026-08-24 00:12 639231264180839154
411 ms 210.79.167.108