DNS response history for ns2.repuestospino.com

ns2.repuestospino.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 28 DNS check records, 27 successful responses, 1 failed responses, and 260 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.repuestospino.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

260 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.31.174.196

Most recently resolved hosting IP on selected date

Successful Responses

27

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

4%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.repuestospino.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
28 2026-08-26 09:13 639233318749762337
236 ms 50.31.174.196
27 2026-08-26 08:56 639233308387917838
278 ms 50.31.174.196
26 2026-08-26 08:38 639233297961740122
246 ms 50.31.174.196
25 2026-08-26 08:21 639233287487159094
252 ms 50.31.174.196
24 2026-08-26 08:03 639233276995531707
268 ms 50.31.174.196
23 2026-08-26 07:46 639233266521568229
252 ms 50.31.174.196
22 2026-08-26 07:28 639233256081047431
231 ms 50.31.174.196
21 2026-08-26 06:35 639233223620132921
226 ms 50.31.174.196
20 2026-08-26 06:17 639233213287814244
318 ms 50.31.174.196
19 2026-08-26 06:00 639233202925983161
259 ms 50.31.174.196
18 2026-08-26 05:43 639233192644780696
243 ms 50.31.174.196
17 2026-08-26 05:26 639233182401183833
240 ms 50.31.174.196
16 2026-08-26 05:09 639233172074181051
234 ms 50.31.174.196
15 2026-08-26 04:51 639233161808421455
268 ms 50.31.174.196
14 2026-08-26 04:34 639233151357344052
231 ms 50.31.174.196
13 2026-08-26 04:17 639233141034116946
320 ms 50.31.174.196
12 2026-08-26 04:00 639233130828334142
-
11 2026-08-26 03:42 639233120373450007
266 ms 50.31.174.196
10 2026-08-26 03:25 639233110066216193
262 ms 50.31.174.196
9 2026-08-26 02:32 639233078065410564
239 ms 50.31.174.196
8 2026-08-26 02:15 639233067787457832
231 ms 50.31.174.196
7 2026-08-26 01:57 639233057501801162
290 ms 50.31.174.196
6 2026-08-26 01:40 639233047089431703
264 ms 50.31.174.196
5 2026-08-26 01:23 639233036754790688
271 ms 50.31.174.196
4 2026-08-26 01:06 639233026412602472
240 ms 50.31.174.196
3 2026-08-26 00:48 639233016064066127
236 ms 50.31.174.196
2 2026-08-26 00:31 639233005922655772
354 ms 50.31.174.196
1 2026-08-26 00:14 639232995672256907
252 ms 50.31.174.196