DNS response history for ns2.iloopcomunicacion.com

ns2.iloopcomunicacion.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-27. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 822 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.iloopcomunicacion.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

822 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.161.98.64

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.iloopcomunicacion.com

Showing DNS history for 2026-08-27 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-27 12:02 639234286253196126
2056 ms 185.161.98.64
35 2026-08-27 11:08 639234253963286387
151 ms 185.161.98.64
34 2026-08-27 10:51 639234243654907465
2072 ms 185.161.98.64
33 2026-08-27 10:34 639234233269654413
20 ms 185.161.98.64
32 2026-08-27 10:16 639234222943951923
4 ms 185.161.98.64
31 2026-08-27 09:59 639234212558002823
118 ms 185.161.98.64
30 2026-08-27 09:42 639234202117531850
98 ms 185.161.98.64
29 2026-08-27 09:24 639234191649612722
216 ms 185.161.98.64
28 2026-08-27 09:07 639234181105879568
126 ms 185.161.98.64
27 2026-08-27 08:49 639234170713214496
2053 ms 185.161.98.64
26 2026-08-27 08:32 639234160341037652
120 ms 185.161.98.64
25 2026-08-27 08:15 639234149799404224
119 ms 185.161.98.64
24 2026-08-27 07:58 639234139553286469
73 ms 185.161.98.64
23 2026-08-27 07:04 639234107183588293
2088 ms 185.161.98.64
22 2026-08-27 06:46 639234096905435724
126 ms 185.161.98.64
21 2026-08-27 06:29 639234086579410775
264 ms 185.161.98.64
20 2026-08-27 06:12 639234076291157956
97 ms 185.161.98.64
19 2026-08-27 05:55 639234065981939454
91 ms 185.161.98.64
18 2026-08-27 05:38 639234055548642997
119 ms 185.161.98.64
17 2026-08-27 05:20 639234045267979603
105 ms 185.161.98.64
16 2026-08-27 05:03 639234034999717463
2050 ms 185.161.98.64
15 2026-08-27 04:46 639234024739225358
210 ms 185.161.98.64
14 2026-08-27 04:29 639234014311170162
2057 ms 185.161.98.64
13 2026-08-27 04:11 639234003806017640
2042 ms 185.161.98.64
12 2026-08-27 03:54 639233993356203030
104 ms 185.161.98.64
11 2026-08-27 03:01 639233961301716608
44 ms 185.161.98.64
10 2026-08-27 02:43 639233950834200647
246 ms 185.161.98.64
9 2026-08-27 02:26 639233940431849026
134 ms 185.161.98.64
8 2026-08-27 02:09 639233930110596398
2071 ms 185.161.98.64
7 2026-08-27 01:51 639233919705434540
81 ms 185.161.98.64
6 2026-08-27 01:34 639233909452807845
92 ms 185.161.98.64
5 2026-08-27 01:17 639233899096420820
122 ms 185.161.98.64
4 2026-08-27 01:00 639233888707824939
2064 ms 185.161.98.64
3 2026-08-27 00:42 639233878461203802
2036 ms 185.161.98.64
2 2026-08-27 00:25 639233868060868209
4064 ms 185.161.98.64
1 2026-08-27 00:07 639233857450922991
2055 ms 185.161.98.64