DNS response history for ns1.nedorogo.by

ns1.nedorogo.by 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 28 DNS check records, 28 successful responses, 0 failed responses, and 134 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.nedorogo.by.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

134 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

85.209.148.124

Most recently resolved hosting IP on selected date

Successful Responses

28

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.nedorogo.by

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
28 2026-08-24 11:45 639231683712487276
90 ms 85.209.148.124
27 2026-08-24 11:28 639231673513573868
2016 ms 85.209.148.124
26 2026-08-24 10:35 639231641791249939
107 ms 85.209.148.124
25 2026-08-24 10:18 639231631866211033
104 ms 85.209.148.124
24 2026-08-24 10:01 639231621644955316
3 ms 85.209.148.124
23 2026-08-24 09:44 639231611478799259
84 ms 85.209.148.124
22 2026-08-24 08:52 639231579923718211
97 ms 85.209.148.124
21 2026-08-24 08:35 639231569810702936
81 ms 85.209.148.124
20 2026-08-24 08:18 639231559762411619
86 ms 85.209.148.124
19 2026-08-24 08:01 639231549663595407
65 ms 85.209.148.124
18 2026-08-24 07:09 639231518076817246
214 ms 85.209.148.124
17 2026-08-24 06:52 639231508078650885
121 ms 85.209.148.124
16 2026-08-24 06:35 639231498210697093
2 ms 85.209.148.124
15 2026-08-24 06:19 639231488109699360
84 ms 85.209.148.124
14 2026-08-24 05:26 639231456772510692
25 ms 85.209.148.124
13 2026-08-24 05:10 639231447084631185
3 ms 85.209.148.124
12 2026-08-24 04:54 639231437208519473
2 ms 85.209.148.124
11 2026-08-24 04:37 639231427209627490
80 ms 85.209.148.124
10 2026-08-24 03:45 639231395791246644
177 ms 85.209.148.124
9 2026-08-24 03:29 639231386075551458
62 ms 85.209.148.124
8 2026-08-24 03:12 639231376208713791
91 ms 85.209.148.124
7 2026-08-24 02:55 639231366170589276
6 ms 85.209.148.124
6 2026-08-24 02:03 639231334732159368
3 ms 85.209.148.124
5 2026-08-24 01:47 639231325035670078
54 ms 85.209.148.124
4 2026-08-24 01:30 639231315132253837
3 ms 85.209.148.124
3 2026-08-24 01:13 639231305014280808
6 ms 85.209.148.124
2 2026-08-24 00:21 639231273779380675
85 ms 85.209.148.124
1 2026-08-24 00:05 639231264180839154
7 ms 85.209.148.124