DNS response history for ns2.imt-systems.com

ns2.imt-systems.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 219 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.imt-systems.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

219 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

82.98.89.220

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.imt-systems.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:14 639233360361507238
32 ms 82.98.89.220
31 2026-08-26 09:57 639233350067824371
40 ms 82.98.89.220
30 2026-08-26 09:39 639233339545274518
18 ms 82.98.89.220
29 2026-08-26 09:22 639233329214918079
12 ms 82.98.89.220
28 2026-08-26 09:05 639233318749762337
32 ms 82.98.89.220
27 2026-08-26 08:47 639233308387917838
49 ms 82.98.89.220
26 2026-08-26 08:30 639233297961740122
22 ms 82.98.89.220
25 2026-08-26 08:13 639233287487159094
2073 ms 82.98.89.220
24 2026-08-26 07:55 639233276995531707
47 ms 82.98.89.220
23 2026-08-26 07:38 639233266521568229
52 ms 82.98.89.220
22 2026-08-26 07:20 639233256081047431
20 ms 82.98.89.220
21 2026-08-26 06:26 639233223620132921
47 ms 82.98.89.220
20 2026-08-26 06:09 639233213287814244
20 ms 82.98.89.220
19 2026-08-26 05:52 639233202925983161
40 ms 82.98.89.220
18 2026-08-26 05:34 639233192644780696
19 ms 82.98.89.220
17 2026-08-26 05:17 639233182401183833
8 ms 82.98.89.220
16 2026-08-26 05:00 639233172074181051
23 ms 82.98.89.220
15 2026-08-26 04:43 639233161808421455
35 ms 82.98.89.220
14 2026-08-26 04:26 639233151357344052
10 ms 82.98.89.220
13 2026-08-26 04:08 639233141034116946
13 ms 82.98.89.220
12 2026-08-26 03:51 639233130828334142
2038 ms 82.98.89.220
11 2026-08-26 03:34 639233120373450007
9 ms 82.98.89.220
10 2026-08-26 03:17 639233110066216193
39 ms 82.98.89.220
9 2026-08-26 02:24 639233078065410564
20 ms 82.98.89.220
8 2026-08-26 02:06 639233067787457832
30 ms 82.98.89.220
7 2026-08-26 01:49 639233057501801162
38 ms 82.98.89.220
6 2026-08-26 01:32 639233047089431703
22 ms 82.98.89.220
5 2026-08-26 01:15 639233036754790688
11 ms 82.98.89.220
4 2026-08-26 00:57 639233026412602472
2054 ms 82.98.89.220
3 2026-08-26 00:40 639233016064066127
89 ms 82.98.89.220
2 2026-08-26 00:23 639233005922655772
18 ms 82.98.89.220
1 2026-08-26 00:06 639232995672256907
24 ms 82.98.89.220