DNS response history for ns1.go4server.in

ns1.go4server.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 38 DNS check records, 38 successful responses, 0 failed responses, and 471 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.go4server.in.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

471 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.50.76.57

Most recently resolved hosting IP on selected date

Successful Responses

38

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.go4server.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
38 2026-08-25 13:16 639232597643611557
201 ms 49.50.76.57
37 2026-08-25 12:58 639232587225721862
201 ms 49.50.76.57
36 2026-08-25 12:41 639232576780683689
970 ms 49.50.76.57
35 2026-08-25 12:24 639232566381512620
808 ms 49.50.76.57
34 2026-08-25 12:06 639232556111768563
208 ms 49.50.76.57
33 2026-08-25 11:49 639232545839529039
410 ms 49.50.76.57
32 2026-08-25 11:32 639232535349285207
199 ms 49.50.76.57
31 2026-08-25 11:14 639232524938080723
197 ms 49.50.76.57
30 2026-08-25 10:21 639232492740373468
405 ms 49.50.76.57
29 2026-08-25 10:04 639232482235303141
3 ms 49.50.76.57
28 2026-08-25 09:46 639232471861770303
406 ms 49.50.76.57
27 2026-08-25 09:29 639232461630217327
409 ms 49.50.76.57
26 2026-08-25 09:12 639232451282965990
205 ms 49.50.76.57
25 2026-08-25 08:54 639232440814614938
411 ms 49.50.76.57
24 2026-08-25 08:37 639232430410720425
211 ms 49.50.76.57
23 2026-08-25 08:20 639232420003096185
406 ms 49.50.76.57
22 2026-08-25 08:02 639232409467287444
358 ms 49.50.76.57
21 2026-08-25 07:45 639232399077195997
204 ms 49.50.76.57
20 2026-08-25 07:27 639232388731528337
209 ms 49.50.76.57
19 2026-08-25 07:10 639232378288598612
405 ms 49.50.76.57
18 2026-08-25 06:16 639232346196373643
2183 ms 49.50.76.57
17 2026-08-25 05:59 639232336112370741
411 ms 49.50.76.57
16 2026-08-25 05:43 639232326146508970
421 ms 49.50.76.57
15 2026-08-25 05:26 639232316189381720
4332 ms 49.50.76.57
14 2026-08-25 05:10 639232306217998913
208 ms 49.50.76.57
13 2026-08-25 04:53 639232296255744174
201 ms 49.50.76.57
12 2026-08-25 04:36 639232286095760789
201 ms 49.50.76.57
11 2026-08-25 04:19 639232276086186273
208 ms 49.50.76.57
10 2026-08-25 04:03 639232265900986425
412 ms 49.50.76.57
9 2026-08-25 03:46 639232255723518075
34 ms 49.50.76.57
8 2026-08-25 03:29 639232245484452890
201 ms 49.50.76.57
7 2026-08-25 03:11 639232235157175331
341 ms 49.50.76.57
6 2026-08-25 02:18 639232203197189095
272 ms 49.50.76.57
5 2026-08-25 02:01 639232192844564298
416 ms 49.50.76.57
4 2026-08-25 01:44 639232182496008942
410 ms 49.50.76.57
3 2026-08-25 01:26 639232172197053132
407 ms 49.50.76.57
2 2026-08-25 00:33 639232140250307418
202 ms 49.50.76.57
1 2026-08-25 00:16 639232129927860324
212 ms 49.50.76.57