DNS response history for ns2.robochat.pro

ns2.robochat.pro 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 472 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.robochat.pro.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

472 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

86.107.233.46

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.robochat.pro

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
56 ms 86.107.233.46
31 2026-08-26 10:00 639233350067824371
406 ms 86.107.233.46
30 2026-08-26 09:43 639233339545274518
35 ms 86.107.233.46
29 2026-08-26 09:25 639233329214918079
90 ms 86.107.233.46
28 2026-08-26 09:08 639233318749762337
64 ms 86.107.233.46
27 2026-08-26 08:51 639233308387917838
96 ms 86.107.233.46
26 2026-08-26 08:33 639233297961740122
2056 ms 86.107.233.46
25 2026-08-26 08:16 639233287487159094
50 ms 86.107.233.46
24 2026-08-26 07:58 639233276995531707
10 ms 86.107.233.46
23 2026-08-26 07:41 639233266521568229
328 ms 86.107.233.46
22 2026-08-26 07:23 639233256081047431
67 ms 86.107.233.46
21 2026-08-26 06:29 639233223620132921
49 ms 86.107.233.46
20 2026-08-26 06:12 639233213287814244
2055 ms 86.107.233.46
19 2026-08-26 05:55 639233202925983161
182 ms 86.107.233.46
18 2026-08-26 05:38 639233192644780696
73 ms 86.107.233.46
17 2026-08-26 05:20 639233182401183833
399 ms 86.107.233.46
16 2026-08-26 05:03 639233172074181051
201 ms 86.107.233.46
15 2026-08-26 04:46 639233161808421455
2040 ms 86.107.233.46
14 2026-08-26 04:29 639233151357344052
331 ms 86.107.233.46
13 2026-08-26 04:12 639233141034116946
87 ms 86.107.233.46
12 2026-08-26 03:55 639233130828334142
2014 ms 86.107.233.46
11 2026-08-26 03:37 639233120373450007
4052 ms 86.107.233.46
10 2026-08-26 03:20 639233110066216193
5 ms 86.107.233.46
9 2026-08-26 02:27 639233078065410564
23 ms 86.107.233.46
8 2026-08-26 02:10 639233067787457832
40 ms 86.107.233.46
7 2026-08-26 01:52 639233057501801162
11 ms 86.107.233.46
6 2026-08-26 01:35 639233047089431703
2 ms 86.107.233.46
5 2026-08-26 01:18 639233036754790688
57 ms 86.107.233.46
4 2026-08-26 01:01 639233026412602472
30 ms 86.107.233.46
3 2026-08-26 00:43 639233016064066127
42 ms 86.107.233.46
2 2026-08-26 00:26 639233005922655772
72 ms 86.107.233.46
1 2026-08-26 00:09 639232995672256907
71 ms 86.107.233.46