DNS response history for n2.serverbyt.in

n2.serverbyt.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 390 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 n2.serverbyt.in.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

390 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.151.30.185

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 n2.serverbyt.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:31 639232576780683689
47 ms 185.151.30.185
35 2026-08-25 12:13 639232566381512620
36 ms 185.151.30.185
34 2026-08-25 11:56 639232556111768563
56 ms 185.151.30.185
33 2026-08-25 11:39 639232545839529039
122 ms 185.151.30.185
32 2026-08-25 11:22 639232535349285207
34 ms 185.151.30.185
31 2026-08-25 11:04 639232524938080723
4248 ms 185.151.30.185
30 2026-08-25 10:11 639232492740373468
2122 ms 185.151.30.185
29 2026-08-25 09:53 639232482235303141
53 ms 185.151.30.185
28 2026-08-25 09:36 639232471861770303
28 ms 185.151.30.185
27 2026-08-25 09:19 639232461630217327
23 ms 185.151.30.185
26 2026-08-25 09:01 639232451282965990
2177 ms 185.151.30.185
25 2026-08-25 08:44 639232440814614938
83 ms 185.151.30.185
24 2026-08-25 08:27 639232430410720425
2026 ms 185.151.30.185
23 2026-08-25 08:09 639232420003096185
119 ms 185.151.30.185
22 2026-08-25 07:52 639232409467287444
27 ms 185.151.30.185
21 2026-08-25 07:34 639232399077195997
16 ms 185.151.30.185
20 2026-08-25 07:17 639232388731528337
33 ms 185.151.30.185
19 2026-08-25 07:00 639232378288598612
38 ms 185.151.30.185
18 2026-08-25 06:06 639232346196373643
51 ms 185.151.30.185
17 2026-08-25 05:49 639232336112370741
20 ms 185.151.30.185
16 2026-08-25 05:33 639232326146508970
120 ms 185.151.30.185
15 2026-08-25 05:16 639232316189381720
15 ms 185.151.30.185
14 2026-08-25 05:00 639232306217998913
37 ms 185.151.30.185
13 2026-08-25 04:43 639232296255744174
50 ms 185.151.30.185
12 2026-08-25 04:26 639232286095760789
2074 ms 185.151.30.185
11 2026-08-25 04:09 639232276086186273
19 ms 185.151.30.185
10 2026-08-25 03:53 639232265900986425
32 ms 185.151.30.185
9 2026-08-25 03:36 639232255723518075
20 ms 185.151.30.185
8 2026-08-25 03:18 639232245484452890
23 ms 185.151.30.185
7 2026-08-25 03:01 639232235157175331
50 ms 185.151.30.185
6 2026-08-25 02:08 639232203197189095
21 ms 185.151.30.185
5 2026-08-25 01:51 639232192844564298
115 ms 185.151.30.185
4 2026-08-25 01:34 639232182496008942
37 ms 185.151.30.185
3 2026-08-25 01:16 639232172197053132
15 ms 185.151.30.185
2 2026-08-25 00:23 639232140250307418
19 ms 185.151.30.185
1 2026-08-25 00:06 639232129927860324
26 ms 185.151.30.185