DNS response history for ns2.session.in

ns2.session.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-25. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 441 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.session.in.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

441 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.169.88

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 ns2.session.in

Showing DNS history for 2026-08-25 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-08-25 12:40 639232576780683689
4 ms 162.240.169.88
35 2026-08-25 12:23 639232566381512620
238 ms 162.240.169.88
34 2026-08-25 12:06 639232556111768563
176 ms 162.240.169.88
33 2026-08-25 11:49 639232545839529039
360 ms 162.240.169.88
32 2026-08-25 11:31 639232535349285207
360 ms 162.240.169.88
31 2026-08-25 11:14 639232524938080723
358 ms 162.240.169.88
30 2026-08-25 10:20 639232492740373468
361 ms 162.240.169.88
29 2026-08-25 10:03 639232482235303141
15 ms 162.240.169.88
28 2026-08-25 09:46 639232471861770303
2008 ms 162.240.169.88
27 2026-08-25 09:28 639232461630217327
352 ms 162.240.169.88
26 2026-08-25 09:11 639232451282965990
2195 ms 162.240.169.88
25 2026-08-25 08:54 639232440814614938
2007 ms 162.240.169.88
24 2026-08-25 08:36 639232430410720425
2187 ms 162.240.169.88
23 2026-08-25 08:19 639232420003096185
360 ms 162.240.169.88
22 2026-08-25 08:02 639232409467287444
177 ms 162.240.169.88
21 2026-08-25 07:44 639232399077195997
175 ms 162.240.169.88
20 2026-08-25 07:27 639232388731528337
353 ms 162.240.169.88
19 2026-08-25 07:10 639232378288598612
359 ms 162.240.169.88
18 2026-08-25 06:16 639232346196373643
361 ms 162.240.169.88
17 2026-08-25 05:59 639232336112370741
7 ms 162.240.169.88
16 2026-08-25 05:42 639232326146508970
166 ms 162.240.169.88
15 2026-08-25 05:26 639232316189381720
170 ms 162.240.169.88
14 2026-08-25 05:09 639232306217998913
2 ms 162.240.169.88
13 2026-08-25 04:53 639232296255744174
3 ms 162.240.169.88
12 2026-08-25 04:36 639232286095760789
364 ms 162.240.169.88
11 2026-08-25 04:19 639232276086186273
170 ms 162.240.169.88
10 2026-08-25 04:02 639232265900986425
348 ms 162.240.169.88
9 2026-08-25 03:45 639232255723518075
347 ms 162.240.169.88
8 2026-08-25 03:28 639232245484452890
347 ms 162.240.169.88
7 2026-08-25 03:11 639232235157175331
344 ms 162.240.169.88
6 2026-08-25 02:18 639232203197189095
345 ms 162.240.169.88
5 2026-08-25 02:01 639232192844564298
170 ms 162.240.169.88
4 2026-08-25 01:43 639232182496008942
7 ms 162.240.169.88
3 2026-08-25 01:26 639232172197053132
173 ms 162.240.169.88
2 2026-08-25 00:33 639232140250307418
346 ms 162.240.169.88
1 2026-08-25 00:16 639232129927860324
171 ms 162.240.169.88