DNS response history for ns1.nebadom.com

ns1.nebadom.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 30 DNS check records, 29 successful responses, 1 failed responses, and 398 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.nebadom.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

398 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

149.56.129.170

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.nebadom.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
30 2026-08-24 12:14 639231703815441688
151 ms 149.56.129.170
29 2026-08-24 11:58 639231693747052549
15 ms 149.56.129.170
28 2026-08-24 11:41 639231683712487276
2040 ms 149.56.129.170
27 2026-08-24 11:24 639231673513573868
9 ms 149.56.129.170
26 2026-08-24 10:31 639231641791249939
116 ms 149.56.129.170
25 2026-08-24 10:14 639231631866211033
12 ms 149.56.129.170
24 2026-08-24 09:57 639231621644955316
12 ms 149.56.129.170
23 2026-08-24 09:40 639231611478799259
10 ms 149.56.129.170
22 2026-08-24 08:48 639231579923718211
19 ms 149.56.129.170
21 2026-08-24 08:31 639231569810702936
141 ms 149.56.129.170
20 2026-08-24 08:14 639231559762411619
13 ms 149.56.129.170
19 2026-08-24 07:57 639231549663595407
24 ms 149.56.129.170
18 2026-08-24 07:05 639231518076817246
105 ms 149.56.129.170
17 2026-08-24 06:48 639231508078650885
212 ms 149.56.129.170
16 2026-08-24 06:32 639231498210697093
-
15 2026-08-24 06:15 639231488109699360
2030 ms 149.56.129.170
14 2026-08-24 05:23 639231456772510692
31 ms 149.56.129.170
13 2026-08-24 05:06 639231447084631185
98 ms 149.56.129.170
12 2026-08-24 04:50 639231437208519473
4072 ms 149.56.129.170
11 2026-08-24 04:33 639231427209627490
43 ms 149.56.129.170
10 2026-08-24 03:41 639231395791246644
22 ms 149.56.129.170
9 2026-08-24 03:25 639231386075551458
62 ms 149.56.129.170
8 2026-08-24 03:08 639231376208713791
7 ms 149.56.129.170
7 2026-08-24 02:52 639231366170589276
114 ms 149.56.129.170
6 2026-08-24 01:59 639231334732159368
13 ms 149.56.129.170
5 2026-08-24 01:43 639231325035670078
64 ms 149.56.129.170
4 2026-08-24 01:27 639231315132253837
2074 ms 149.56.129.170
3 2026-08-24 01:10 639231305014280808
8 ms 149.56.129.170
2 2026-08-24 00:18 639231273779380675
5 ms 149.56.129.170
1 2026-08-24 00:02 639231264180839154
13 ms 149.56.129.170