DNS response history for ns2.idlservice.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

441 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.109.255.51

Most recently resolved hosting IP on selected date

Successful Responses

36

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.idlservice.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
36 2026-08-26 11:56 639233414056832719
18 ms 208.109.255.51
35 2026-08-26 11:38 639233403515141099
20 ms 208.109.255.51
34 2026-08-26 10:43 639233370841350248
19 ms 208.109.255.51
33 2026-08-26 10:26 639233360361507238
2019 ms 208.109.255.51
32 2026-08-26 10:09 639233350067824371
10 ms 208.109.255.51
31 2026-08-26 09:52 639233339545274518
18 ms 208.109.255.51
30 2026-08-26 09:34 639233329214918079
21 ms 208.109.255.51
29 2026-08-26 09:17 639233318749762337
23 ms 208.109.255.51
28 2026-08-26 08:59 639233308387917838
22 ms 208.109.255.51
27 2026-08-26 08:42 639233297961740122
452 ms 208.109.255.51
26 2026-08-26 08:25 639233287487159094
2032 ms 208.109.255.51
25 2026-08-26 08:07 639233276995531707
19 ms 208.109.255.51
24 2026-08-26 07:50 639233266521568229
77 ms 208.109.255.51
23 2026-08-26 07:32 639233256081047431
31 ms 208.109.255.51
22 2026-08-26 06:38 639233223620132921
17 ms 208.109.255.51
21 2026-08-26 06:21 639233213287814244
15 ms 208.109.255.51
20 2026-08-26 06:04 639233202925983161
2129 ms 208.109.255.51
19 2026-08-26 05:46 639233192644780696
16 ms 208.109.255.51
18 2026-08-26 05:29 639233182401183833
17 ms 208.109.255.51
17 2026-08-26 05:12 639233172074181051
41 ms 208.109.255.51
16 2026-08-26 04:55 639233161808421455
29 ms 208.109.255.51
15 2026-08-26 04:38 639233151357344052
2035 ms 208.109.255.51
14 2026-08-26 04:20 639233141034116946
18 ms 208.109.255.51
13 2026-08-26 04:03 639233130828334142
19 ms 208.109.255.51
12 2026-08-26 03:46 639233120373450007
17 ms 208.109.255.51
11 2026-08-26 03:29 639233110066216193
17 ms 208.109.255.51
10 2026-08-26 02:36 639233078065410564
18 ms 208.109.255.51
9 2026-08-26 02:18 639233067787457832
418 ms 208.109.255.51
8 2026-08-26 02:01 639233057501801162
17 ms 208.109.255.51
7 2026-08-26 01:44 639233047089431703
44 ms 208.109.255.51
6 2026-08-26 01:27 639233036754790688
22 ms 208.109.255.51
5 2026-08-26 01:10 639233026412602472
20 ms 208.109.255.51
4 2026-08-26 00:52 639233016064066127
16 ms 208.109.255.51
3 2026-08-26 00:35 639233005922655772
2030 ms 208.109.255.51
2 2026-08-26 00:18 639232995672256907
117 ms 208.109.255.51
1 2026-08-26 00:01 639232985300872416
4017 ms 208.109.255.51