DNS response history for ns2.thebigleaf.com

ns2.thebigleaf.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-28. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 274 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.thebigleaf.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

274 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 12:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.29.131.6

Most recently resolved hosting IP on selected date

Successful Responses

29

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

Showing DNS history for 2026-08-28 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
29 2026-08-28 12:34 639235163898672622
309 ms 66.29.131.6
28 2026-08-28 11:41 639235132147470568
304 ms 66.29.131.6
27 2026-08-28 11:24 639235121907744088
313 ms 66.29.131.6
26 2026-08-28 11:07 639235111428014262
320 ms 66.29.131.6
25 2026-08-28 10:49 639235100921813626
292 ms 66.29.131.6
24 2026-08-28 09:55 639235068670703481
322 ms 66.29.131.6
23 2026-08-28 09:38 639235058337459445
303 ms 66.29.131.6
22 2026-08-28 09:21 639235047825109146
304 ms 66.29.131.6
21 2026-08-28 09:03 639235037383229033
320 ms 66.29.131.6
20 2026-08-28 08:10 639235005619242711
310 ms 66.29.131.6
19 2026-08-28 07:53 639234995310346584
289 ms 66.29.131.6
18 2026-08-28 07:36 639234984946548933
321 ms 66.29.131.6
17 2026-08-28 07:19 639234974608077290
299 ms 66.29.131.6
16 2026-08-28 06:25 639234942529845595
295 ms 66.29.131.6
15 2026-08-28 06:08 639234932259126627
293 ms 66.29.131.6
14 2026-08-28 05:51 639234921916735988
3 ms 66.29.131.6
13 2026-08-28 05:34 639234911470038027
311 ms 66.29.131.6
12 2026-08-28 04:40 639234879588411654
287 ms 66.29.131.6
11 2026-08-28 04:23 639234869341589104
329 ms 66.29.131.6
10 2026-08-28 04:06 639234859012216675
304 ms 66.29.131.6
9 2026-08-28 03:49 639234848695364934
2 ms 66.29.131.6
8 2026-08-28 02:56 639234816952458162
294 ms 66.29.131.6
7 2026-08-28 02:39 639234806773081598
299 ms 66.29.131.6
6 2026-08-28 02:22 639234796382955255
3 ms 66.29.131.6
5 2026-08-28 02:04 639234786015782563
294 ms 66.29.131.6
4 2026-08-28 01:11 639234753811917646
332 ms 66.29.131.6
3 2026-08-28 00:54 639234743739767811
300 ms 66.29.131.6
2 2026-08-28 00:37 639234733372362811
307 ms 66.29.131.6
1 2026-08-28 00:19 639234723048550337
293 ms 66.29.131.6