DNS response history for ns1.revamz.com

ns1.revamz.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 35 DNS check records, 35 successful responses, 0 failed responses, and 595 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.revamz.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

595 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

82.165.210.180

Most recently resolved hosting IP on selected date

Successful Responses

35

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.revamz.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
35 2026-08-25 12:07 639232556111768563
675 ms 82.165.210.180
34 2026-08-25 11:50 639232545839529039
736 ms 82.165.210.180
33 2026-08-25 11:33 639232535349285207
793 ms 82.165.210.180
32 2026-08-25 11:16 639232524938080723
763 ms 82.165.210.180
31 2026-08-25 10:22 639232492740373468
762 ms 82.165.210.180
30 2026-08-25 10:05 639232482235303141
778 ms 82.165.210.180
29 2026-08-25 09:47 639232471861770303
801 ms 82.165.210.180
28 2026-08-25 09:30 639232461630217327
823 ms 82.165.210.180
27 2026-08-25 09:13 639232451282965990
5 ms 82.165.210.180
26 2026-08-25 08:56 639232440814614938
820 ms 82.165.210.180
25 2026-08-25 08:38 639232430410720425
19 ms 82.165.210.180
24 2026-08-25 08:21 639232420003096185
5 ms 82.165.210.180
23 2026-08-25 08:03 639232409467287444
729 ms 82.165.210.180
22 2026-08-25 07:46 639232399077195997
807 ms 82.165.210.180
21 2026-08-25 07:29 639232388731528337
5 ms 82.165.210.180
20 2026-08-25 07:11 639232378288598612
853 ms 82.165.210.180
19 2026-08-25 06:17 639232346196373643
735 ms 82.165.210.180
18 2026-08-25 06:01 639232336112370741
850 ms 82.165.210.180
17 2026-08-25 05:44 639232326146508970
814 ms 82.165.210.180
16 2026-08-25 05:27 639232316189381720
6 ms 82.165.210.180
15 2026-08-25 05:11 639232306217998913
674 ms 82.165.210.180
14 2026-08-25 04:54 639232296255744174
789 ms 82.165.210.180
13 2026-08-25 04:37 639232286095760789
40 ms 82.165.210.180
12 2026-08-25 04:20 639232276086186273
820 ms 82.165.210.180
11 2026-08-25 04:04 639232265900986425
7 ms 82.165.210.180
10 2026-08-25 03:47 639232255723518075
770 ms 82.165.210.180
9 2026-08-25 03:30 639232245484452890
690 ms 82.165.210.180
8 2026-08-25 03:13 639232235157175331
819 ms 82.165.210.180
7 2026-08-25 02:19 639232203197189095
262 ms 82.165.210.180
6 2026-08-25 02:02 639232192844564298
808 ms 82.165.210.180
5 2026-08-25 01:45 639232182496008942
817 ms 82.165.210.180
4 2026-08-25 01:28 639232172197053132
654 ms 82.165.210.180
3 2026-08-25 00:34 639232140250307418
774 ms 82.165.210.180
2 2026-08-25 00:17 639232129927860324
731 ms 82.165.210.180
1 2026-08-25 00:00 639232119551972438
403 ms 82.165.210.180