DNS response history for ns2.wavoram.com

ns2.wavoram.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-25. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 1247 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.wavoram.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

1247 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.28.50.210

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 ns2.wavoram.com

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
37 2026-08-25 12:43 639232576780683689
2111 ms 50.28.50.210
36 2026-08-25 12:26 639232566381512620
2117 ms 50.28.50.210
35 2026-08-25 12:08 639232556111768563
2136 ms 50.28.50.210
34 2026-08-25 11:51 639232545839529039
2032 ms 50.28.50.210
33 2026-08-25 11:34 639232535349285207
2127 ms 50.28.50.210
32 2026-08-25 11:17 639232524938080723
2111 ms 50.28.50.210
31 2026-08-25 10:23 639232492740373468
129 ms 50.28.50.210
30 2026-08-25 10:06 639232482235303141
2032 ms 50.28.50.210
29 2026-08-25 09:48 639232471861770303
2045 ms 50.28.50.210
28 2026-08-25 09:31 639232461630217327
2125 ms 50.28.50.210
27 2026-08-25 09:14 639232451282965990
132 ms 50.28.50.210
26 2026-08-25 08:57 639232440814614938
138 ms 50.28.50.210
25 2026-08-25 08:39 639232430410720425
2124 ms 50.28.50.210
24 2026-08-25 08:22 639232420003096185
2227 ms 50.28.50.210
23 2026-08-25 08:04 639232409467287444
221 ms 50.28.50.210
22 2026-08-25 07:47 639232399077195997
2119 ms 50.28.50.210
21 2026-08-25 07:30 639232388731528337
2159 ms 50.28.50.210
20 2026-08-25 07:12 639232378288598612
162 ms 50.28.50.210
19 2026-08-25 06:18 639232346196373643
2128 ms 50.28.50.210
18 2026-08-25 06:02 639232336112370741
2032 ms 50.28.50.210
17 2026-08-25 05:45 639232326146508970
3 ms 50.28.50.210
16 2026-08-25 05:28 639232316189381720
2 ms 50.28.50.210
15 2026-08-25 05:12 639232306217998913
3 ms 50.28.50.210
14 2026-08-25 04:55 639232296255744174
131 ms 50.28.50.210
13 2026-08-25 04:38 639232286095760789
129 ms 50.28.50.210
12 2026-08-25 04:21 639232276086186273
2111 ms 50.28.50.210
11 2026-08-25 04:05 639232265900986425
132 ms 50.28.50.210
10 2026-08-25 03:48 639232255723518075
129 ms 50.28.50.210
9 2026-08-25 03:31 639232245484452890
2033 ms 50.28.50.210
8 2026-08-25 03:14 639232235157175331
2228 ms 50.28.50.210
7 2026-08-25 02:20 639232203197189095
126 ms 50.28.50.210
6 2026-08-25 02:03 639232192844564298
131 ms 50.28.50.210
5 2026-08-25 01:46 639232182496008942
2136 ms 50.28.50.210
4 2026-08-25 01:29 639232172197053132
146 ms 50.28.50.210
3 2026-08-25 00:35 639232140250307418
2034 ms 50.28.50.210
2 2026-08-25 00:18 639232129927860324
2127 ms 50.28.50.210
1 2026-08-25 00:01 639232119551972438
125 ms 50.28.50.210