DNS response history for burlap.tv

burlap.tv 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 38 DNS check records, 38 successful responses, 0 failed responses, and 194 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 burlap.tv.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

194 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.63.8.121

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 burlap.tv

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
38 2026-08-25 13:04 639232597643611557
15 ms 50.63.8.121
37 2026-08-25 12:47 639232587225721862
17 ms 50.63.8.121
36 2026-08-25 12:29 639232576780683689
47 ms 50.63.8.121
35 2026-08-25 12:12 639232566381512620
53 ms 50.63.8.121
34 2026-08-25 11:55 639232556111768563
132 ms 50.63.8.121
33 2026-08-25 11:38 639232545839529039
41 ms 50.63.8.121
32 2026-08-25 11:20 639232535349285207
66 ms 50.63.8.121
31 2026-08-25 11:03 639232524938080723
24 ms 50.63.8.121
30 2026-08-25 10:09 639232492740373468
30 ms 50.63.8.121
29 2026-08-25 09:52 639232482235303141
47 ms 50.63.8.121
28 2026-08-25 09:34 639232471861770303
38 ms 50.63.8.121
27 2026-08-25 09:17 639232461630217327
106 ms 50.63.8.121
26 2026-08-25 09:00 639232451282965990
43 ms 50.63.8.121
25 2026-08-25 08:43 639232440814614938
31 ms 50.63.8.121
24 2026-08-25 08:25 639232430410720425
33 ms 50.63.8.121
23 2026-08-25 08:08 639232420003096185
45 ms 50.63.8.121
22 2026-08-25 07:50 639232409467287444
39 ms 50.63.8.121
21 2026-08-25 07:33 639232399077195997
12 ms 50.63.8.121
20 2026-08-25 07:16 639232388731528337
2020 ms 50.63.8.121
19 2026-08-25 06:58 639232378288598612
2029 ms 50.63.8.121
18 2026-08-25 06:05 639232346196373643
14 ms 50.63.8.121
17 2026-08-25 05:48 639232336112370741
26 ms 50.63.8.121
16 2026-08-25 05:31 639232326146508970
49 ms 50.63.8.121
15 2026-08-25 05:15 639232316189381720
36 ms 50.63.8.121
14 2026-08-25 04:58 639232306217998913
42 ms 50.63.8.121
13 2026-08-25 04:42 639232296255744174
32 ms 50.63.8.121
12 2026-08-25 04:25 639232286095760789
12 ms 50.63.8.121
11 2026-08-25 04:08 639232276086186273
2014 ms 50.63.8.121
10 2026-08-25 03:51 639232265900986425
34 ms 50.63.8.121
9 2026-08-25 03:34 639232255723518075
13 ms 50.63.8.121
8 2026-08-25 03:17 639232245484452890
23 ms 50.63.8.121
7 2026-08-25 03:00 639232235157175331
35 ms 50.63.8.121
6 2026-08-25 02:07 639232203197189095
43 ms 50.63.8.121
5 2026-08-25 01:49 639232192844564298
27 ms 50.63.8.121
4 2026-08-25 01:32 639232182496008942
21 ms 50.63.8.121
3 2026-08-25 01:15 639232172197053132
25 ms 50.63.8.121
2 2026-08-25 00:22 639232140250307418
24 ms 50.63.8.121
1 2026-08-25 00:04 639232129927860324
24 ms 50.63.8.121