DNS response history for ns2.resultados-ya.futbol

ns2.resultados-ya.futbol 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 31 DNS check records, 31 successful responses, 0 failed responses, and 440 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.resultados-ya.futbol.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

440 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.214.144.123

Most recently resolved hosting IP on selected date

Successful Responses

31

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.resultados-ya.futbol

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
31 2026-08-26 10:07 639233350067824371
342 ms 162.214.144.123
30 2026-08-26 09:50 639233339545274518
170 ms 162.214.144.123
29 2026-08-26 09:32 639233329214918079
2159 ms 162.214.144.123
28 2026-08-26 09:15 639233318749762337
174 ms 162.214.144.123
27 2026-08-26 08:58 639233308387917838
351 ms 162.214.144.123
26 2026-08-26 08:40 639233297961740122
171 ms 162.214.144.123
25 2026-08-26 08:23 639233287487159094
157 ms 162.214.144.123
24 2026-08-26 08:05 639233276995531707
452 ms 162.214.144.123
23 2026-08-26 07:48 639233266521568229
455 ms 162.214.144.123
22 2026-08-26 07:30 639233256081047431
348 ms 162.214.144.123
21 2026-08-26 06:37 639233223620132921
343 ms 162.214.144.123
20 2026-08-26 06:19 639233213287814244
170 ms 162.214.144.123
19 2026-08-26 06:02 639233202925983161
172 ms 162.214.144.123
18 2026-08-26 05:45 639233192644780696
455 ms 162.214.144.123
17 2026-08-26 05:27 639233182401183833
461 ms 162.214.144.123
16 2026-08-26 05:11 639233172074181051
2032 ms 162.214.144.123
15 2026-08-26 04:53 639233161808421455
4 ms 162.214.144.123
14 2026-08-26 04:36 639233151357344052
2 ms 162.214.144.123
13 2026-08-26 04:19 639233141034116946
337 ms 162.214.144.123
12 2026-08-26 04:02 639233130828334142
346 ms 162.214.144.123
11 2026-08-26 03:44 639233120373450007
2007 ms 162.214.144.123
10 2026-08-26 03:27 639233110066216193
346 ms 162.214.144.123
9 2026-08-26 02:34 639233078065410564
448 ms 162.214.144.123
8 2026-08-26 02:17 639233067787457832
505 ms 162.214.144.123
7 2026-08-26 01:59 639233057501801162
166 ms 162.214.144.123
6 2026-08-26 01:42 639233047089431703
171 ms 162.214.144.123
5 2026-08-26 01:25 639233036754790688
8 ms 162.214.144.123
4 2026-08-26 01:08 639233026412602472
170 ms 162.214.144.123
3 2026-08-26 00:50 639233016064066127
342 ms 162.214.144.123
2 2026-08-26 00:33 639233005922655772
170 ms 162.214.144.123
1 2026-08-26 00:16 639232995672256907
193 ms 162.214.144.123