DNS response history for ns383.dnsever.com

ns383.dnsever.com 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-28. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 199 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 ns383.dnsever.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

199 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 15:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.38.97.137

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns383.dnsever.com

Showing DNS history for 2026-08-28 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
37 2026-08-28 15:56 639235291168160936
2035 ms 51.38.97.137
36 2026-08-28 15:02 639235258803654519
28 ms 51.38.97.137
35 2026-08-28 14:45 639235248596087996
26 ms 51.38.97.137
34 2026-08-28 14:28 639235238225955920
22 ms 51.38.97.137
33 2026-08-28 14:11 639235227727862105
2024 ms 51.38.97.137
32 2026-08-28 13:16 639235195230848570
2018 ms 51.38.97.137
31 2026-08-28 12:59 639235184840503274
37 ms 51.38.97.137
30 2026-08-28 12:42 639235174453894956
43 ms 51.38.97.137
29 2026-08-28 12:24 639235163898672622
40 ms 51.38.97.137
28 2026-08-28 11:31 639235132147470568
21 ms 51.38.97.137
27 2026-08-28 11:14 639235121907744088
51 ms 51.38.97.137
26 2026-08-28 10:57 639235111428014262
13 ms 51.38.97.137
25 2026-08-28 10:39 639235100921813626
67 ms 51.38.97.137
24 2026-08-28 09:45 639235068670703481
136 ms 51.38.97.137
23 2026-08-28 09:28 639235058337459445
50 ms 51.38.97.137
22 2026-08-28 09:11 639235047825109146
42 ms 51.38.97.137
21 2026-08-28 08:53 639235037383229033
24 ms 51.38.97.137
20 2026-08-28 08:00 639235005619242711
34 ms 51.38.97.137
19 2026-08-28 07:43 639234995310346584
35 ms 51.38.97.137
18 2026-08-28 07:26 639234984946548933
34 ms 51.38.97.137
17 2026-08-28 07:09 639234974608077290
31 ms 51.38.97.137
16 2026-08-28 06:15 639234942529845595
82 ms 51.38.97.137
15 2026-08-28 05:58 639234932259126627
38 ms 51.38.97.137
14 2026-08-28 05:41 639234921916735988
23 ms 51.38.97.137
13 2026-08-28 05:24 639234911470038027
40 ms 51.38.97.137
12 2026-08-28 04:30 639234879588411654
27 ms 51.38.97.137
11 2026-08-28 04:13 639234869341589104
23 ms 51.38.97.137
10 2026-08-28 03:56 639234859012216675
24 ms 51.38.97.137
9 2026-08-28 03:39 639234848695364934
58 ms 51.38.97.137
8 2026-08-28 02:46 639234816952458162
4 ms 51.38.97.137
7 2026-08-28 02:29 639234806773081598
31 ms 51.38.97.137
6 2026-08-28 02:12 639234796382955255
54 ms 51.38.97.137
5 2026-08-28 01:54 639234786015782563
14 ms 51.38.97.137
4 2026-08-28 01:01 639234753811917646
37 ms 51.38.97.137
3 2026-08-28 00:44 639234743739767811
23 ms 51.38.97.137
2 2026-08-28 00:27 639234733372362811
35 ms 51.38.97.137
1 2026-08-28 00:09 639234723048550337
35 ms 51.38.97.137