DNS response history for ns2.niversal.net

ns2.niversal.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-24. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 389 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.niversal.net.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

389 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

187.9.79.254

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

Showing DNS history for 2026-08-24 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-24 13:51 639231755868832964
148 ms 187.9.79.254
32 2026-08-24 13:34 639231745628278877
794 ms 187.9.79.254
31 2026-08-24 13:17 639231735407682062
301 ms 187.9.79.254
30 2026-08-24 12:24 639231703815441688
296 ms 187.9.79.254
29 2026-08-24 12:08 639231693747052549
300 ms 187.9.79.254
28 2026-08-24 11:51 639231683712487276
4 ms 187.9.79.254
27 2026-08-24 11:34 639231673513573868
146 ms 187.9.79.254
26 2026-08-24 10:41 639231641791249939
242 ms 187.9.79.254
25 2026-08-24 10:24 639231631866211033
65 ms 187.9.79.254
24 2026-08-24 10:08 639231621644955316
295 ms 187.9.79.254
23 2026-08-24 09:51 639231611478799259
296 ms 187.9.79.254
22 2026-08-24 08:58 639231579923718211
2 ms 187.9.79.254
21 2026-08-24 08:41 639231569810702936
943 ms 187.9.79.254
20 2026-08-24 08:24 639231559762411619
310 ms 187.9.79.254
19 2026-08-24 08:07 639231549663595407
305 ms 187.9.79.254
18 2026-08-24 07:15 639231518076817246
4 ms 187.9.79.254
17 2026-08-24 06:58 639231508078650885
330 ms 187.9.79.254
16 2026-08-24 06:42 639231498210697093
156 ms 187.9.79.254
15 2026-08-24 06:25 639231488109699360
298 ms 187.9.79.254
14 2026-08-24 05:33 639231456772510692
293 ms 187.9.79.254
13 2026-08-24 05:16 639231447084631185
293 ms 187.9.79.254
12 2026-08-24 05:00 639231437208519473
236 ms 187.9.79.254
11 2026-08-24 04:43 639231427209627490
228 ms 187.9.79.254
10 2026-08-24 03:51 639231395791246644
324 ms 187.9.79.254
9 2026-08-24 03:35 639231386075551458
1965 ms 187.9.79.254
8 2026-08-24 03:18 639231376208713791
209 ms 187.9.79.254
7 2026-08-24 03:02 639231366170589276
295 ms 187.9.79.254
6 2026-08-24 02:09 639231334732159368
234 ms 187.9.79.254
5 2026-08-24 01:53 639231325035670078
369 ms 187.9.79.254
4 2026-08-24 01:37 639231315132253837
227 ms 187.9.79.254
3 2026-08-24 01:20 639231305014280808
881 ms 187.9.79.254
2 2026-08-24 00:28 639231273779380675
1732 ms 187.9.79.254
1 2026-08-24 00:12 639231264180839154
303 ms 187.9.79.254