DNS response history for ns3.verpex.com

ns3.verpex.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-24. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 260 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 ns3.verpex.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

260 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

76.223.26.245

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns3.verpex.com

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
34 2026-08-24 13:56 639231765923559455
8 ms 76.223.26.245
33 2026-08-24 13:40 639231755868832964
16 ms 76.223.26.245
32 2026-08-24 13:23 639231745628278877
26 ms 76.223.26.245
31 2026-08-24 13:06 639231735407682062
24 ms 76.223.26.245
30 2026-08-24 12:13 639231703815441688
27 ms 76.223.26.245
29 2026-08-24 11:56 639231693747052549
26 ms 76.223.26.245
28 2026-08-24 11:39 639231683712487276
40 ms 76.223.26.245
27 2026-08-24 11:22 639231673513573868
2043 ms 76.223.26.245
26 2026-08-24 10:29 639231641791249939
44 ms 76.223.26.245
25 2026-08-24 10:13 639231631866211033
7 ms 76.223.26.245
24 2026-08-24 09:56 639231621644955316
2031 ms 76.223.26.245
23 2026-08-24 09:39 639231611478799259
19 ms 76.223.26.245
22 2026-08-24 08:46 639231579923718211
2015 ms 76.223.26.245
21 2026-08-24 08:30 639231569810702936
68 ms 76.223.26.245
20 2026-08-24 08:13 639231559762411619
21 ms 76.223.26.245
19 2026-08-24 07:56 639231549663595407
2023 ms 76.223.26.245
18 2026-08-24 07:03 639231518076817246
32 ms 76.223.26.245
17 2026-08-24 06:47 639231508078650885
29 ms 76.223.26.245
16 2026-08-24 06:30 639231498210697093
22 ms 76.223.26.245
15 2026-08-24 06:13 639231488109699360
9 ms 76.223.26.245
14 2026-08-24 05:21 639231456772510692
35 ms 76.223.26.245
13 2026-08-24 05:05 639231447084631185
15 ms 76.223.26.245
12 2026-08-24 04:49 639231437208519473
7 ms 76.223.26.245
11 2026-08-24 04:32 639231427209627490
6 ms 76.223.26.245
10 2026-08-24 03:39 639231395791246644
7 ms 76.223.26.245
9 2026-08-24 03:23 639231386075551458
10 ms 76.223.26.245
8 2026-08-24 03:07 639231376208713791
8 ms 76.223.26.245
7 2026-08-24 02:50 639231366170589276
5 ms 76.223.26.245
6 2026-08-24 01:58 639231334732159368
38 ms 76.223.26.245
5 2026-08-24 01:42 639231325035670078
40 ms 76.223.26.245
4 2026-08-24 01:25 639231315132253837
22 ms 76.223.26.245
3 2026-08-24 01:08 639231305014280808
20 ms 76.223.26.245
2 2026-08-24 00:16 639231273779380675
47 ms 76.223.26.245
1 2026-08-24 00:00 639231264180839154
48 ms 76.223.26.245