DNS response history for ns2.digsim.net

ns2.digsim.net 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 34 DNS check records, 34 successful responses, 0 failed responses, and 476 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.digsim.net.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

476 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 14:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.168.10.146

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.digsim.net

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
34 2026-08-28 14:34 639235238225955920
138 ms 192.168.10.146
33 2026-08-28 14:17 639235227727862105
272 ms 192.168.10.146
32 2026-08-28 13:22 639235195230848570
255 ms 192.168.10.146
31 2026-08-28 13:05 639235184840503274
2008 ms 192.168.10.146
30 2026-08-28 12:48 639235174453894956
135 ms 192.168.10.146
29 2026-08-28 12:30 639235163898672622
255 ms 192.168.10.146
28 2026-08-28 11:37 639235132147470568
257 ms 192.168.10.146
27 2026-08-28 11:20 639235121907744088
256 ms 192.168.10.146
26 2026-08-28 11:03 639235111428014262
267 ms 192.168.10.146
25 2026-08-28 10:45 639235100921813626
254 ms 192.168.10.146
24 2026-08-28 09:51 639235068670703481
268 ms 192.168.10.146
23 2026-08-28 09:34 639235058337459445
253 ms 192.168.10.146
22 2026-08-28 09:17 639235047825109146
2032 ms 192.168.10.146
21 2026-08-28 08:59 639235037383229033
256 ms 192.168.10.146
20 2026-08-28 08:06 639235005619242711
134 ms 192.168.10.146
19 2026-08-28 07:49 639234995310346584
257 ms 192.168.10.146
18 2026-08-28 07:32 639234984946548933
2126 ms 192.168.10.146
17 2026-08-28 07:15 639234974608077290
2008 ms 192.168.10.146
16 2026-08-28 06:21 639234942529845595
255 ms 192.168.10.146
15 2026-08-28 06:04 639234932259126627
252 ms 192.168.10.146
14 2026-08-28 05:47 639234921916735988
262 ms 192.168.10.146
13 2026-08-28 05:30 639234911470038027
267 ms 192.168.10.146
12 2026-08-28 04:36 639234879588411654
253 ms 192.168.10.146
11 2026-08-28 04:19 639234869341589104
255 ms 192.168.10.146
10 2026-08-28 04:02 639234859012216675
32 ms 192.168.10.146
9 2026-08-28 03:45 639234848695364934
3 ms 192.168.10.146
8 2026-08-28 02:52 639234816952458162
255 ms 192.168.10.146
7 2026-08-28 02:35 639234806773081598
370 ms 192.168.10.146
6 2026-08-28 02:18 639234796382955255
2149 ms 192.168.10.146
5 2026-08-28 02:00 639234786015782563
258 ms 192.168.10.146
4 2026-08-28 01:07 639234753811917646
127 ms 192.168.10.146
3 2026-08-28 00:50 639234743739767811
2 ms 192.168.10.146
2 2026-08-28 00:33 639234733372362811
3 ms 192.168.10.146
1 2026-08-28 00:15 639234723048550337
3 ms 192.168.10.146