DNS response history for ns3.novosibirsk.city

ns3.novosibirsk.city 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-09-01. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 233 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 ns3.novosibirsk.city.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

233 ms

Calculated from available response records

Latest Check on Selected Date

2026-09-01 12:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.136.98.77

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns3.novosibirsk.city

Showing DNS history for 2026-09-01 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
36 2026-09-01 12:34 639238628486902752
31 ms 185.136.98.77
35 2026-09-01 12:16 639238617906743100
14 ms 185.136.98.77
34 2026-09-01 11:59 639238607506044626
17 ms 185.136.98.77
33 2026-09-01 11:42 639238597040761406
5 ms 185.136.98.77
32 2026-09-01 11:24 639238586261546969
10 ms 185.136.98.77
31 2026-09-01 11:06 639238575587642333
25 ms 185.136.98.77
30 2026-09-01 10:12 639238543127398267
13 ms 185.136.98.77
29 2026-09-01 09:54 639238532668234016
2143 ms 185.136.98.77
28 2026-09-01 09:37 639238522029321761
9 ms 185.136.98.77
27 2026-09-01 09:19 639238511519050351
2517 ms 185.136.98.77
26 2026-09-01 09:02 639238500942239673
26 ms 185.136.98.77
25 2026-09-01 08:44 639238490412377398
12 ms 185.136.98.77
24 2026-09-01 08:26 639238479833203021
306 ms 185.136.98.77
23 2026-09-01 08:09 639238469140507479
28 ms 185.136.98.77
22 2026-09-01 07:51 639238458443560361
7 ms 185.136.98.77
21 2026-09-01 07:33 639238447694851502
459 ms 185.136.98.77
20 2026-09-01 07:14 639238436624109087
17 ms 185.136.98.77
19 2026-09-01 06:56 639238425565611335
32 ms 185.136.98.77
18 2026-09-01 06:00 639238392250222581
21 ms 185.136.98.77
17 2026-09-01 05:42 639238381322537831
186 ms 185.136.98.77
16 2026-09-01 05:24 639238370248186084
3 ms 185.136.98.77
15 2026-09-01 05:05 639238359264687845
4 ms 185.136.98.77
14 2026-09-01 04:48 639238348534621818
10 ms 185.136.98.77
13 2026-09-01 04:30 639238337725739433
4 ms 185.136.98.77
12 2026-09-01 04:11 639238326844749368
29 ms 185.136.98.77
11 2026-09-01 03:53 639238315792024737
43 ms 185.136.98.77
10 2026-09-01 03:35 639238304931064768
38 ms 185.136.98.77
9 2026-09-01 03:17 639238294131483803
18 ms 185.136.98.77
8 2026-09-01 02:59 639238283314985519
44 ms 185.136.98.77
7 2026-09-01 02:41 639238272374093187
14 ms 185.136.98.77
6 2026-09-01 01:47 639238240032549922
21 ms 185.136.98.77
5 2026-09-01 01:29 639238229204177368
40 ms 185.136.98.77
4 2026-09-01 01:11 639238218326150282
19 ms 185.136.98.77
3 2026-09-01 00:53 639238207574700853
42 ms 185.136.98.77
2 2026-09-01 00:34 639238196660283915
2181 ms 185.136.98.77
1 2026-09-01 00:16 639238185782358546
13 ms 185.136.98.77