DNS response history for ns2.geolvo.club

ns2.geolvo.club 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-26. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 492 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.geolvo.club.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

492 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

109.201.133.61

Most recently resolved hosting IP on selected date

Successful Responses

32

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.geolvo.club

Showing DNS history for 2026-08-26 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
32 2026-08-26 10:17 639233360361507238
19 ms 109.201.133.61
31 2026-08-26 10:00 639233350067824371
93 ms 109.201.133.61
30 2026-08-26 09:43 639233339545274518
85 ms 109.201.133.61
29 2026-08-26 09:25 639233329214918079
58 ms 109.201.133.61
28 2026-08-26 09:08 639233318749762337
22 ms 109.201.133.61
27 2026-08-26 08:51 639233308387917838
41 ms 109.201.133.61
26 2026-08-26 08:33 639233297961740122
74 ms 109.201.133.61
25 2026-08-26 08:16 639233287487159094
27 ms 109.201.133.61
24 2026-08-26 07:58 639233276995531707
45 ms 109.201.133.61
23 2026-08-26 07:41 639233266521568229
2014 ms 109.201.133.61
22 2026-08-26 07:24 639233256081047431
66 ms 109.201.133.61
21 2026-08-26 06:30 639233223620132921
4012 ms 109.201.133.61
20 2026-08-26 06:12 639233213287814244
62 ms 109.201.133.61
19 2026-08-26 05:55 639233202925983161
2065 ms 109.201.133.61
18 2026-08-26 05:38 639233192644780696
38 ms 109.201.133.61
17 2026-08-26 05:21 639233182401183833
42 ms 109.201.133.61
16 2026-08-26 05:04 639233172074181051
2024 ms 109.201.133.61
15 2026-08-26 04:46 639233161808421455
45 ms 109.201.133.61
14 2026-08-26 04:29 639233151357344052
39 ms 109.201.133.61
13 2026-08-26 04:12 639233141034116946
53 ms 109.201.133.61
12 2026-08-26 03:55 639233130828334142
24 ms 109.201.133.61
11 2026-08-26 03:37 639233120373450007
2020 ms 109.201.133.61
10 2026-08-26 03:20 639233110066216193
70 ms 109.201.133.61
9 2026-08-26 02:27 639233078065410564
191 ms 109.201.133.61
8 2026-08-26 02:10 639233067787457832
123 ms 109.201.133.61
7 2026-08-26 01:53 639233057501801162
2012 ms 109.201.133.61
6 2026-08-26 01:35 639233047089431703
49 ms 109.201.133.61
5 2026-08-26 01:18 639233036754790688
63 ms 109.201.133.61
4 2026-08-26 01:01 639233026412602472
102 ms 109.201.133.61
3 2026-08-26 00:44 639233016064066127
48 ms 109.201.133.61
2 2026-08-26 00:27 639233005922655772
96 ms 109.201.133.61
1 2026-08-26 00:10 639232995672256907
7 ms 109.201.133.61