DNS response history for ns2.robotkeyautomation.com

ns2.robotkeyautomation.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 32 DNS check records, 32 successful responses, 0 failed responses, and 565 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.robotkeyautomation.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

565 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.180.121.111

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.robotkeyautomation.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
32 2026-08-26 10:23 639233360361507238
272 ms 103.180.121.111
31 2026-08-26 10:06 639233350067824371
287 ms 103.180.121.111
30 2026-08-26 09:49 639233339545274518
277 ms 103.180.121.111
29 2026-08-26 09:31 639233329214918079
302 ms 103.180.121.111
28 2026-08-26 09:14 639233318749762337
281 ms 103.180.121.111
27 2026-08-26 08:57 639233308387917838
2008 ms 103.180.121.111
26 2026-08-26 08:39 639233297961740122
2270 ms 103.180.121.111
25 2026-08-26 08:22 639233287487159094
280 ms 103.180.121.111
24 2026-08-26 08:05 639233276995531707
2139 ms 103.180.121.111
23 2026-08-26 07:47 639233266521568229
281 ms 103.180.121.111
22 2026-08-26 07:29 639233256081047431
166 ms 103.180.121.111
21 2026-08-26 06:36 639233223620132921
264 ms 103.180.121.111
20 2026-08-26 06:18 639233213287814244
257 ms 103.180.121.111
19 2026-08-26 06:01 639233202925983161
280 ms 103.180.121.111
18 2026-08-26 05:44 639233192644780696
284 ms 103.180.121.111
17 2026-08-26 05:27 639233182401183833
282 ms 103.180.121.111
16 2026-08-26 05:10 639233172074181051
281 ms 103.180.121.111
15 2026-08-26 04:52 639233161808421455
275 ms 103.180.121.111
14 2026-08-26 04:35 639233151357344052
158 ms 103.180.121.111
13 2026-08-26 04:18 639233141034116946
269 ms 103.180.121.111
12 2026-08-26 04:01 639233130828334142
288 ms 103.180.121.111
11 2026-08-26 03:43 639233120373450007
269 ms 103.180.121.111
10 2026-08-26 03:26 639233110066216193
271 ms 103.180.121.111
9 2026-08-26 02:33 639233078065410564
2352 ms 103.180.121.111
8 2026-08-26 02:16 639233067787457832
294 ms 103.180.121.111
7 2026-08-26 01:59 639233057501801162
2144 ms 103.180.121.111
6 2026-08-26 01:41 639233047089431703
273 ms 103.180.121.111
5 2026-08-26 01:24 639233036754790688
287 ms 103.180.121.111
4 2026-08-26 01:07 639233026412602472
286 ms 103.180.121.111
3 2026-08-26 00:49 639233016064066127
142 ms 103.180.121.111
2 2026-08-26 00:32 639233005922655772
279 ms 103.180.121.111
1 2026-08-26 00:15 639232995672256907
287 ms 103.180.121.111