DNS response history for my.fam.ly

my.fam.ly 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-25. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 578 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 my.fam.ly.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

578 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

45.33.120.172

Most recently resolved hosting IP on selected date

Successful Responses

37

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 my.fam.ly

Showing DNS history for 2026-08-25 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
37 2026-08-25 12:54 639232587225721862
213 ms 45.33.120.172
36 2026-08-25 12:37 639232576780683689
216 ms 45.33.120.172
35 2026-08-25 12:20 639232566381512620
450 ms 45.33.120.172
34 2026-08-25 12:02 639232556111768563
207 ms 45.33.120.172
33 2026-08-25 11:45 639232545839529039
128 ms 45.33.120.172
32 2026-08-25 11:28 639232535349285207
205 ms 45.33.120.172
31 2026-08-25 11:11 639232524938080723
222 ms 45.33.120.172
30 2026-08-25 10:17 639232492740373468
205 ms 45.33.120.172
29 2026-08-25 10:00 639232482235303141
162 ms 45.33.120.172
28 2026-08-25 09:42 639232471861770303
202 ms 45.33.120.172
27 2026-08-25 09:25 639232461630217327
200 ms 45.33.120.172
26 2026-08-25 09:08 639232451282965990
2007 ms 45.33.120.172
25 2026-08-25 08:50 639232440814614938
147 ms 45.33.120.172
24 2026-08-25 08:33 639232430410720425
240 ms 45.33.120.172
23 2026-08-25 08:16 639232420003096185
2118 ms 45.33.120.172
22 2026-08-25 07:58 639232409467287444
2131 ms 45.33.120.172
21 2026-08-25 07:41 639232399077195997
203 ms 45.33.120.172
20 2026-08-25 07:24 639232388731528337
441 ms 45.33.120.172
19 2026-08-25 07:06 639232378288598612
251 ms 45.33.120.172
18 2026-08-25 06:13 639232346196373643
202 ms 45.33.120.172
17 2026-08-25 05:56 639232336112370741
199 ms 45.33.120.172
16 2026-08-25 05:39 639232326146508970
202 ms 45.33.120.172
15 2026-08-25 05:23 639232316189381720
219 ms 45.33.120.172
14 2026-08-25 05:06 639232306217998913
238 ms 45.33.120.172
13 2026-08-25 04:49 639232296255744174
4 ms 45.33.120.172
12 2026-08-25 04:32 639232286095760789
2158 ms 45.33.120.172
11 2026-08-25 04:16 639232276086186273
217 ms 45.33.120.172
10 2026-08-25 03:59 639232265900986425
2112 ms 45.33.120.172
9 2026-08-25 03:42 639232255723518075
203 ms 45.33.120.172
8 2026-08-25 03:25 639232245484452890
2212 ms 45.33.120.172
7 2026-08-25 03:08 639232235157175331
205 ms 45.33.120.172
6 2026-08-25 02:14 639232203197189095
242 ms 45.33.120.172
5 2026-08-25 01:57 639232192844564298
201 ms 45.33.120.172
4 2026-08-25 01:40 639232182496008942
206 ms 45.33.120.172
3 2026-08-25 01:23 639232172197053132
2114 ms 45.33.120.172
2 2026-08-25 00:29 639232140250307418
287 ms 45.33.120.172
1 2026-08-25 00:12 639232129927860324
202 ms 45.33.120.172