DNS response history for ns2.hopesudan.org

ns2.hopesudan.org 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 33 DNS check records, 33 successful responses, 0 failed responses, and 386 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.hopesudan.org.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

386 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

173.249.34.46

Most recently resolved hosting IP on selected date

Successful Responses

33

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.hopesudan.org

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
33 2026-08-25 11:39 639232545839529039
50 ms 173.249.34.46
32 2026-08-25 11:22 639232535349285207
26 ms 173.249.34.46
31 2026-08-25 11:04 639232524938080723
18 ms 173.249.34.46
30 2026-08-25 10:11 639232492740373468
16 ms 173.249.34.46
29 2026-08-25 09:53 639232482235303141
80 ms 173.249.34.46
28 2026-08-25 09:36 639232471861770303
46 ms 173.249.34.46
27 2026-08-25 09:19 639232461630217327
240 ms 173.249.34.46
26 2026-08-25 09:02 639232451282965990
2025 ms 173.249.34.46
25 2026-08-25 08:44 639232440814614938
164 ms 173.249.34.46
24 2026-08-25 08:27 639232430410720425
4031 ms 173.249.34.46
23 2026-08-25 08:10 639232420003096185
28 ms 173.249.34.46
22 2026-08-25 07:52 639232409467287444
21 ms 173.249.34.46
21 2026-08-25 07:35 639232399077195997
190 ms 173.249.34.46
20 2026-08-25 07:17 639232388731528337
2325 ms 173.249.34.46
19 2026-08-25 07:00 639232378288598612
277 ms 173.249.34.46
18 2026-08-25 06:07 639232346196373643
19 ms 173.249.34.46
17 2026-08-25 05:50 639232336112370741
58 ms 173.249.34.46
16 2026-08-25 05:33 639232326146508970
45 ms 173.249.34.46
15 2026-08-25 05:17 639232316189381720
56 ms 173.249.34.46
14 2026-08-25 05:00 639232306217998913
68 ms 173.249.34.46
13 2026-08-25 04:43 639232296255744174
5 ms 173.249.34.46
12 2026-08-25 04:26 639232286095760789
20 ms 173.249.34.46
11 2026-08-25 04:10 639232276086186273
3 ms 173.249.34.46
10 2026-08-25 03:53 639232265900986425
45 ms 173.249.34.46
9 2026-08-25 03:36 639232255723518075
54 ms 173.249.34.46
8 2026-08-25 03:19 639232245484452890
43 ms 173.249.34.46
7 2026-08-25 03:02 639232235157175331
44 ms 173.249.34.46
6 2026-08-25 02:08 639232203197189095
270 ms 173.249.34.46
5 2026-08-25 01:51 639232192844564298
57 ms 173.249.34.46
4 2026-08-25 01:34 639232182496008942
42 ms 173.249.34.46
3 2026-08-25 01:17 639232172197053132
321 ms 173.249.34.46
2 2026-08-25 00:23 639232140250307418
33 ms 173.249.34.46
1 2026-08-25 00:06 639232129927860324
2012 ms 173.249.34.46