DNS response history for ns2.fableshore.com

ns2.fableshore.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-30. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 331 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.fableshore.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

331 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 10:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.81.68.228

Most recently resolved hosting IP on selected date

Successful Responses

32

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.fableshore.com

Showing DNS history for 2026-08-30 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
32 2026-08-30 10:43 639236827967386881
133 ms 74.81.68.228
31 2026-08-30 10:26 639236817708615077
4 ms 74.81.68.228
30 2026-08-30 09:33 639236785770651804
278 ms 74.81.68.228
29 2026-08-30 09:16 639236775820686373
266 ms 74.81.68.228
28 2026-08-30 08:59 639236765768339082
7 ms 74.81.68.228
27 2026-08-30 08:43 639236755602384085
2138 ms 74.81.68.228
26 2026-08-30 08:26 639236745600094925
277 ms 74.81.68.228
25 2026-08-30 08:09 639236735311262753
285 ms 74.81.68.228
24 2026-08-30 07:52 639236724996745235
268 ms 74.81.68.228
23 2026-08-30 07:35 639236714839899761
136 ms 74.81.68.228
22 2026-08-30 07:18 639236704748431488
20 ms 74.81.68.228
21 2026-08-30 07:01 639236694430128550
133 ms 74.81.68.228
20 2026-08-30 06:44 639236684143292417
285 ms 74.81.68.228
19 2026-08-30 06:26 639236673972499943
273 ms 74.81.68.228
18 2026-08-30 05:33 639236642126522802
267 ms 74.81.68.228
17 2026-08-30 05:17 639236632183518198
257 ms 74.81.68.228
16 2026-08-30 05:00 639236622289312589
149 ms 74.81.68.228
15 2026-08-30 04:44 639236612490676525
2145 ms 74.81.68.228
14 2026-08-30 04:27 639236602582494852
231 ms 74.81.68.228
13 2026-08-30 04:11 639236592511706469
290 ms 74.81.68.228
12 2026-08-30 03:54 639236582441006869
143 ms 74.81.68.228
11 2026-08-30 03:37 639236572478785089
129 ms 74.81.68.228
10 2026-08-30 03:21 639236562556749999
268 ms 74.81.68.228
9 2026-08-30 03:04 639236552353482281
274 ms 74.81.68.228
8 2026-08-30 02:47 639236542188881607
271 ms 74.81.68.228
7 2026-08-30 02:30 639236531885440105
140 ms 74.81.68.228
6 2026-08-30 01:36 639236499922985383
273 ms 74.81.68.228
5 2026-08-30 01:20 639236489713594431
281 ms 74.81.68.228
4 2026-08-30 01:03 639236479750443901
272 ms 74.81.68.228
3 2026-08-30 00:46 639236469719936375
270 ms 74.81.68.228
2 2026-08-30 00:29 639236459579244885
271 ms 74.81.68.228
1 2026-08-30 00:12 639236449582837549
145 ms 74.81.68.228