DNS response history for ns2.mydiablito.com

ns2.mydiablito.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 37 DNS check records, 36 successful responses, 1 failed responses, and 348 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.mydiablito.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

348 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

99.83.188.187

Most recently resolved hosting IP on selected date

Successful Responses

36

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.mydiablito.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
37 2026-08-26 12:19 639233434974187439
2054 ms 99.83.188.187
36 2026-08-26 12:02 639233424567558554
69 ms 99.83.188.187
35 2026-08-26 11:44 639233414056832719
112 ms 99.83.188.187
34 2026-08-26 11:27 639233403515141099
-
33 2026-08-26 10:32 639233370841350248
39 ms 99.83.188.187
32 2026-08-26 10:15 639233360361507238
74 ms 99.83.188.187
31 2026-08-26 09:57 639233350067824371
72 ms 99.83.188.187
30 2026-08-26 09:40 639233339545274518
4056 ms 99.83.188.187
29 2026-08-26 09:23 639233329214918079
34 ms 99.83.188.187
28 2026-08-26 09:05 639233318749762337
2100 ms 99.83.188.187
27 2026-08-26 08:48 639233308387917838
62 ms 99.83.188.187
26 2026-08-26 08:30 639233297961740122
50 ms 99.83.188.187
25 2026-08-26 08:13 639233287487159094
56 ms 99.83.188.187
24 2026-08-26 07:56 639233276995531707
64 ms 99.83.188.187
23 2026-08-26 07:38 639233266521568229
45 ms 99.83.188.187
22 2026-08-26 07:21 639233256081047431
122 ms 99.83.188.187
21 2026-08-26 06:27 639233223620132921
74 ms 99.83.188.187
20 2026-08-26 06:09 639233213287814244
68 ms 99.83.188.187
19 2026-08-26 05:52 639233202925983161
83 ms 99.83.188.187
18 2026-08-26 05:35 639233192644780696
79 ms 99.83.188.187
17 2026-08-26 05:18 639233182401183833
81 ms 99.83.188.187
16 2026-08-26 05:01 639233172074181051
40 ms 99.83.188.187
15 2026-08-26 04:44 639233161808421455
113 ms 99.83.188.187
14 2026-08-26 04:26 639233151357344052
102 ms 99.83.188.187
13 2026-08-26 04:09 639233141034116946
66 ms 99.83.188.187
12 2026-08-26 03:52 639233130828334142
82 ms 99.83.188.187
11 2026-08-26 03:34 639233120373450007
62 ms 99.83.188.187
10 2026-08-26 03:17 639233110066216193
12 ms 99.83.188.187
9 2026-08-26 02:24 639233078065410564
94 ms 99.83.188.187
8 2026-08-26 02:07 639233067787457832
68 ms 99.83.188.187
7 2026-08-26 01:50 639233057501801162
10 ms 99.83.188.187
6 2026-08-26 01:32 639233047089431703
60 ms 99.83.188.187
5 2026-08-26 01:15 639233036754790688
64 ms 99.83.188.187
4 2026-08-26 00:58 639233026412602472
77 ms 99.83.188.187
3 2026-08-26 00:41 639233016064066127
93 ms 99.83.188.187
2 2026-08-26 00:24 639233005922655772
127 ms 99.83.188.187
1 2026-08-26 00:07 639232995672256907
2077 ms 99.83.188.187