DNS response history for b.ns.rehime.com.ar

b.ns.rehime.com.ar 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 38 DNS check records, 38 successful responses, 0 failed responses, and 572 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 b.ns.rehime.com.ar.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

572 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

119.8.76.65

Most recently resolved hosting IP on selected date

Successful Responses

38

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 b.ns.rehime.com.ar

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
38 2026-08-26 12:32 639233434974187439
242 ms 119.8.76.65
37 2026-08-26 12:15 639233424567558554
729 ms 119.8.76.65
36 2026-08-26 11:58 639233414056832719
714 ms 119.8.76.65
35 2026-08-26 11:40 639233403515141099
723 ms 119.8.76.65
34 2026-08-26 10:45 639233370841350248
716 ms 119.8.76.65
33 2026-08-26 10:28 639233360361507238
485 ms 119.8.76.65
32 2026-08-26 10:11 639233350067824371
715 ms 119.8.76.65
31 2026-08-26 09:54 639233339545274518
475 ms 119.8.76.65
30 2026-08-26 09:36 639233329214918079
234 ms 119.8.76.65
29 2026-08-26 09:19 639233318749762337
482 ms 119.8.76.65
28 2026-08-26 09:01 639233308387917838
480 ms 119.8.76.65
27 2026-08-26 08:44 639233297961740122
484 ms 119.8.76.65
26 2026-08-26 08:27 639233287487159094
478 ms 119.8.76.65
25 2026-08-26 08:09 639233276995531707
715 ms 119.8.76.65
24 2026-08-26 07:52 639233266521568229
477 ms 119.8.76.65
23 2026-08-26 07:34 639233256081047431
715 ms 119.8.76.65
22 2026-08-26 06:40 639233223620132921
722 ms 119.8.76.65
21 2026-08-26 06:23 639233213287814244
716 ms 119.8.76.65
20 2026-08-26 06:06 639233202925983161
480 ms 119.8.76.65
19 2026-08-26 05:48 639233192644780696
484 ms 119.8.76.65
18 2026-08-26 05:31 639233182401183833
477 ms 119.8.76.65
17 2026-08-26 05:14 639233172074181051
714 ms 119.8.76.65
16 2026-08-26 04:57 639233161808421455
707 ms 119.8.76.65
15 2026-08-26 04:40 639233151357344052
720 ms 119.8.76.65
14 2026-08-26 04:22 639233141034116946
242 ms 119.8.76.65
13 2026-08-26 04:05 639233130828334142
238 ms 119.8.76.65
12 2026-08-26 03:48 639233120373450007
472 ms 119.8.76.65
11 2026-08-26 03:31 639233110066216193
474 ms 119.8.76.65
10 2026-08-26 02:37 639233078065410564
713 ms 119.8.76.65
9 2026-08-26 02:20 639233067787457832
715 ms 119.8.76.65
8 2026-08-26 02:03 639233057501801162
710 ms 119.8.76.65
7 2026-08-26 01:46 639233047089431703
736 ms 119.8.76.65
6 2026-08-26 01:29 639233036754790688
238 ms 119.8.76.65
5 2026-08-26 01:11 639233026412602472
710 ms 119.8.76.65
4 2026-08-26 00:54 639233016064066127
714 ms 119.8.76.65
3 2026-08-26 00:37 639233005922655772
472 ms 119.8.76.65
2 2026-08-26 00:20 639232995672256907
712 ms 119.8.76.65
1 2026-08-26 00:03 639232985300872416
705 ms 119.8.76.65