DNS response history for geo2.dinofly.com

geo2.dinofly.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-26. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 319 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 geo2.dinofly.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

319 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

64.44.171.87

Most recently resolved hosting IP on selected date

Successful Responses

30

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 geo2.dinofly.com

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
30 2026-08-26 09:50 639233339545274518
7 ms 64.44.171.87
29 2026-08-26 09:32 639233329214918079
2097 ms 64.44.171.87
28 2026-08-26 09:15 639233318749762337
126 ms 64.44.171.87
27 2026-08-26 08:58 639233308387917838
251 ms 64.44.171.87
26 2026-08-26 08:40 639233297961740122
253 ms 64.44.171.87
25 2026-08-26 08:23 639233287487159094
246 ms 64.44.171.87
24 2026-08-26 08:06 639233276995531707
249 ms 64.44.171.87
23 2026-08-26 07:48 639233266521568229
247 ms 64.44.171.87
22 2026-08-26 07:30 639233256081047431
258 ms 64.44.171.87
21 2026-08-26 06:37 639233223620132921
121 ms 64.44.171.87
20 2026-08-26 06:19 639233213287814244
247 ms 64.44.171.87
19 2026-08-26 06:02 639233202925983161
102 ms 64.44.171.87
18 2026-08-26 05:45 639233192644780696
123 ms 64.44.171.87
17 2026-08-26 05:28 639233182401183833
250 ms 64.44.171.87
16 2026-08-26 05:11 639233172074181051
125 ms 64.44.171.87
15 2026-08-26 04:53 639233161808421455
243 ms 64.44.171.87
14 2026-08-26 04:36 639233151357344052
239 ms 64.44.171.87
13 2026-08-26 04:19 639233141034116946
246 ms 64.44.171.87
12 2026-08-26 04:02 639233130828334142
124 ms 64.44.171.87
11 2026-08-26 03:45 639233120373450007
860 ms 64.44.171.87
10 2026-08-26 03:27 639233110066216193
122 ms 64.44.171.87
9 2026-08-26 02:34 639233078065410564
238 ms 64.44.171.87
8 2026-08-26 02:17 639233067787457832
244 ms 64.44.171.87
7 2026-08-26 02:00 639233057501801162
123 ms 64.44.171.87
6 2026-08-26 01:42 639233047089431703
125 ms 64.44.171.87
5 2026-08-26 01:25 639233036754790688
2030 ms 64.44.171.87
4 2026-08-26 01:08 639233026412602472
7 ms 64.44.171.87
3 2026-08-26 00:51 639233016064066127
246 ms 64.44.171.87
2 2026-08-26 00:33 639233005922655772
14 ms 64.44.171.87
1 2026-08-26 00:16 639232995672256907
10 ms 64.44.171.87