DNS response history for ns2.juarezimpresores.com

ns2.juarezimpresores.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 34 DNS check records, 33 successful responses, 1 failed responses, and 198 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.juarezimpresores.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

198 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.127.130.137

Most recently resolved hosting IP on selected date

Successful Responses

33

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.juarezimpresores.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
34 2026-08-27 10:52 639234243654907465
94 ms 185.127.130.137
33 2026-08-27 10:35 639234233269654413
69 ms 185.127.130.137
32 2026-08-27 10:18 639234222943951923
125 ms 185.127.130.137
31 2026-08-27 10:00 639234212558002823
154 ms 185.127.130.137
30 2026-08-27 09:43 639234202117531850
133 ms 185.127.130.137
29 2026-08-27 09:26 639234191649612722
94 ms 185.127.130.137
28 2026-08-27 09:08 639234181105879568
33 ms 185.127.130.137
27 2026-08-27 08:51 639234170713214496
92 ms 185.127.130.137
26 2026-08-27 08:33 639234160341037652
41 ms 185.127.130.137
25 2026-08-27 08:16 639234149799404224
94 ms 185.127.130.137
24 2026-08-27 07:59 639234139553286469
-
23 2026-08-27 07:05 639234107183588293
73 ms 185.127.130.137
22 2026-08-27 06:48 639234096905435724
130 ms 185.127.130.137
21 2026-08-27 06:31 639234086579410775
12 ms 185.127.130.137
20 2026-08-27 06:13 639234076291157956
81 ms 185.127.130.137
19 2026-08-27 05:56 639234065981939454
63 ms 185.127.130.137
18 2026-08-27 05:39 639234055548642997
89 ms 185.127.130.137
17 2026-08-27 05:22 639234045267979603
40 ms 185.127.130.137
16 2026-08-27 05:05 639234034999717463
70 ms 185.127.130.137
15 2026-08-27 04:47 639234024739225358
85 ms 185.127.130.137
14 2026-08-27 04:30 639234014311170162
72 ms 185.127.130.137
13 2026-08-27 04:13 639234003806017640
104 ms 185.127.130.137
12 2026-08-27 03:55 639233993356203030
2052 ms 185.127.130.137
11 2026-08-27 03:02 639233961301716608
70 ms 185.127.130.137
10 2026-08-27 02:45 639233950834200647
66 ms 185.127.130.137
9 2026-08-27 02:27 639233940431849026
29 ms 185.127.130.137
8 2026-08-27 02:10 639233930110596398
10 ms 185.127.130.137
7 2026-08-27 01:52 639233919705434540
94 ms 185.127.130.137
6 2026-08-27 01:35 639233909452807845
76 ms 185.127.130.137
5 2026-08-27 01:18 639233899096420820
81 ms 185.127.130.137
4 2026-08-27 01:01 639233888707824939
80 ms 185.127.130.137
3 2026-08-27 00:44 639233878461203802
94 ms 185.127.130.137
2 2026-08-27 00:26 639233868060868209
2059 ms 185.127.130.137
1 2026-08-27 00:09 639233857450922991
74 ms 185.127.130.137