DNS response history for ns1.jansevanrensburg.net

ns1.jansevanrensburg.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-25. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 205 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.jansevanrensburg.net.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

205 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

139.162.231.205

Most recently resolved hosting IP on selected date

Successful Responses

27

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

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
27 2026-08-25 09:19 639232461630217327
80 ms 139.162.231.205
26 2026-08-25 09:01 639232451282965990
57 ms 139.162.231.205
25 2026-08-25 08:44 639232440814614938
55 ms 139.162.231.205
24 2026-08-25 08:27 639232430410720425
2057 ms 139.162.231.205
23 2026-08-25 08:09 639232420003096185
41 ms 139.162.231.205
22 2026-08-25 07:52 639232409467287444
57 ms 139.162.231.205
21 2026-08-25 07:34 639232399077195997
47 ms 139.162.231.205
20 2026-08-25 07:17 639232388731528337
41 ms 139.162.231.205
19 2026-08-25 07:00 639232378288598612
229 ms 139.162.231.205
18 2026-08-25 06:06 639232346196373643
50 ms 139.162.231.205
17 2026-08-25 05:49 639232336112370741
67 ms 139.162.231.205
16 2026-08-25 05:33 639232326146508970
72 ms 139.162.231.205
15 2026-08-25 05:16 639232316189381720
29 ms 139.162.231.205
14 2026-08-25 05:00 639232306217998913
47 ms 139.162.231.205
13 2026-08-25 04:43 639232296255744174
44 ms 139.162.231.205
12 2026-08-25 04:26 639232286095760789
54 ms 139.162.231.205
11 2026-08-25 04:09 639232276086186273
83 ms 139.162.231.205
10 2026-08-25 03:52 639232265900986425
66 ms 139.162.231.205
9 2026-08-25 03:35 639232255723518075
43 ms 139.162.231.205
8 2026-08-25 03:18 639232245484452890
2033 ms 139.162.231.205
7 2026-08-25 03:01 639232235157175331
31 ms 139.162.231.205
6 2026-08-25 02:08 639232203197189095
50 ms 139.162.231.205
5 2026-08-25 01:51 639232192844564298
43 ms 139.162.231.205
4 2026-08-25 01:33 639232182496008942
68 ms 139.162.231.205
3 2026-08-25 01:16 639232172197053132
7 ms 139.162.231.205
2 2026-08-25 00:23 639232140250307418
47 ms 139.162.231.205
1 2026-08-25 00:06 639232129927860324
45 ms 139.162.231.205