DNS response history for ns2.t2resolve.com

ns2.t2resolve.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 423 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.t2resolve.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

423 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.185.223.166

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.t2resolve.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:24 639233360361507238
284 ms 192.185.223.166
31 2026-08-26 10:06 639233350067824371
149 ms 192.185.223.166
30 2026-08-26 09:49 639233339545274518
387 ms 192.185.223.166
29 2026-08-26 09:31 639233329214918079
145 ms 192.185.223.166
28 2026-08-26 09:14 639233318749762337
324 ms 192.185.223.166
27 2026-08-26 08:57 639233308387917838
7 ms 192.185.223.166
26 2026-08-26 08:40 639233297961740122
177 ms 192.185.223.166
25 2026-08-26 08:22 639233287487159094
204 ms 192.185.223.166
24 2026-08-26 08:05 639233276995531707
291 ms 192.185.223.166
23 2026-08-26 07:47 639233266521568229
302 ms 192.185.223.166
22 2026-08-26 07:30 639233256081047431
306 ms 192.185.223.166
21 2026-08-26 06:36 639233223620132921
3 ms 192.185.223.166
20 2026-08-26 06:18 639233213287814244
161 ms 192.185.223.166
19 2026-08-26 06:01 639233202925983161
292 ms 192.185.223.166
18 2026-08-26 05:44 639233192644780696
2237 ms 192.185.223.166
17 2026-08-26 05:27 639233182401183833
2219 ms 192.185.223.166
16 2026-08-26 05:10 639233172074181051
287 ms 192.185.223.166
15 2026-08-26 04:53 639233161808421455
297 ms 192.185.223.166
14 2026-08-26 04:35 639233151357344052
286 ms 192.185.223.166
13 2026-08-26 04:18 639233141034116946
201 ms 192.185.223.166
12 2026-08-26 04:01 639233130828334142
204 ms 192.185.223.166
11 2026-08-26 03:44 639233120373450007
154 ms 192.185.223.166
10 2026-08-26 03:26 639233110066216193
2261 ms 192.185.223.166
9 2026-08-26 02:33 639233078065410564
287 ms 192.185.223.166
8 2026-08-26 02:16 639233067787457832
282 ms 192.185.223.166
7 2026-08-26 01:59 639233057501801162
290 ms 192.185.223.166
6 2026-08-26 01:41 639233047089431703
287 ms 192.185.223.166
5 2026-08-26 01:24 639233036754790688
172 ms 192.185.223.166
4 2026-08-26 01:07 639233026412602472
281 ms 192.185.223.166
3 2026-08-26 00:50 639233016064066127
154 ms 192.185.223.166
2 2026-08-26 00:33 639233005922655772
321 ms 192.185.223.166
1 2026-08-26 00:16 639232995672256907
289 ms 192.185.223.166