DNS response history for ns2.ncode.in

ns2.ncode.in 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-27. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 536 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.ncode.in.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

536 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.20.104.169

Most recently resolved hosting IP on selected date

Successful Responses

34

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.ncode.in

Showing DNS history for 2026-08-27 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
34 2026-08-27 10:59 639234243654907465
245 ms 103.20.104.169
33 2026-08-27 10:41 639234233269654413
247 ms 103.20.104.169
32 2026-08-27 10:24 639234222943951923
4 ms 103.20.104.169
31 2026-08-27 10:07 639234212558002823
275 ms 103.20.104.169
30 2026-08-27 09:50 639234202117531850
1414 ms 103.20.104.169
29 2026-08-27 09:32 639234191649612722
252 ms 103.20.104.169
28 2026-08-27 09:15 639234181105879568
265 ms 103.20.104.169
27 2026-08-27 08:57 639234170713214496
2329 ms 103.20.104.169
26 2026-08-27 08:40 639234160341037652
828 ms 103.20.104.169
25 2026-08-27 08:23 639234149799404224
1427 ms 103.20.104.169
24 2026-08-27 08:05 639234139553286469
313 ms 103.20.104.169
23 2026-08-27 07:11 639234107183588293
253 ms 103.20.104.169
22 2026-08-27 06:54 639234096905435724
245 ms 103.20.104.169
21 2026-08-27 06:37 639234086579410775
270 ms 103.20.104.169
20 2026-08-27 06:20 639234076291157956
257 ms 103.20.104.169
19 2026-08-27 06:03 639234065981939454
248 ms 103.20.104.169
18 2026-08-27 05:45 639234055548642997
279 ms 103.20.104.169
17 2026-08-27 05:28 639234045267979603
832 ms 103.20.104.169
16 2026-08-27 05:11 639234034999717463
263 ms 103.20.104.169
15 2026-08-27 04:54 639234024739225358
264 ms 103.20.104.169
14 2026-08-27 04:37 639234014311170162
260 ms 103.20.104.169
13 2026-08-27 04:19 639234003806017640
1419 ms 103.20.104.169
12 2026-08-27 04:02 639233993356203030
273 ms 103.20.104.169
11 2026-08-27 03:08 639233961301716608
1425 ms 103.20.104.169
10 2026-08-27 02:51 639233950834200647
842 ms 103.20.104.169
9 2026-08-27 02:34 639233940431849026
267 ms 103.20.104.169
8 2026-08-27 02:16 639233930110596398
837 ms 103.20.104.169
7 2026-08-27 01:59 639233919705434540
240 ms 103.20.104.169
6 2026-08-27 01:42 639233909452807845
259 ms 103.20.104.169
5 2026-08-27 01:25 639233899096420820
264 ms 103.20.104.169
4 2026-08-27 01:07 639233888707824939
272 ms 103.20.104.169
3 2026-08-27 00:50 639233878461203802
832 ms 103.20.104.169
2 2026-08-27 00:33 639233868060868209
272 ms 103.20.104.169
1 2026-08-27 00:15 639233857450922991
259 ms 103.20.104.169