DNS response history for ns1.bigsendy.com

ns1.bigsendy.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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 642 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 ns1.bigsendy.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

642 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.69.36.116

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns1.bigsendy.com

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
35 2026-08-26 11:40 639233403515141099
727 ms 202.69.36.116
34 2026-08-26 10:45 639233370841350248
2519 ms 202.69.36.116
33 2026-08-26 10:28 639233360361507238
1044 ms 202.69.36.116
32 2026-08-26 10:11 639233350067824371
260 ms 202.69.36.116
31 2026-08-26 09:54 639233339545274518
273 ms 202.69.36.116
30 2026-08-26 09:36 639233329214918079
1044 ms 202.69.36.116
29 2026-08-26 09:19 639233318749762337
187 ms 202.69.36.116
28 2026-08-26 09:01 639233308387917838
187 ms 202.69.36.116
27 2026-08-26 08:44 639233297961740122
745 ms 202.69.36.116
26 2026-08-26 08:27 639233287487159094
725 ms 202.69.36.116
25 2026-08-26 08:09 639233276995531707
1053 ms 202.69.36.116
24 2026-08-26 07:52 639233266521568229
749 ms 202.69.36.116
23 2026-08-26 07:34 639233256081047431
1078 ms 202.69.36.116
22 2026-08-26 06:40 639233223620132921
1050 ms 202.69.36.116
21 2026-08-26 06:23 639233213287814244
189 ms 202.69.36.116
20 2026-08-26 06:06 639233202925983161
184 ms 202.69.36.116
19 2026-08-26 05:48 639233192644780696
191 ms 202.69.36.116
18 2026-08-26 05:31 639233182401183833
196 ms 202.69.36.116
17 2026-08-26 05:14 639233172074181051
739 ms 202.69.36.116
16 2026-08-26 04:57 639233161808421455
1056 ms 202.69.36.116
15 2026-08-26 04:40 639233151357344052
190 ms 202.69.36.116
14 2026-08-26 04:22 639233141034116946
3 ms 202.69.36.116
13 2026-08-26 04:05 639233130828334142
741 ms 202.69.36.116
12 2026-08-26 03:48 639233120373450007
5 ms 202.69.36.116
11 2026-08-26 03:31 639233110066216193
1048 ms 202.69.36.116
10 2026-08-26 02:37 639233078065410564
4 ms 202.69.36.116
9 2026-08-26 02:20 639233067787457832
3 ms 202.69.36.116
8 2026-08-26 02:03 639233057501801162
258 ms 202.69.36.116
7 2026-08-26 01:46 639233047089431703
1066 ms 202.69.36.116
6 2026-08-26 01:29 639233036754790688
270 ms 202.69.36.116
5 2026-08-26 01:12 639233026412602472
1041 ms 202.69.36.116
4 2026-08-26 00:54 639233016064066127
1072 ms 202.69.36.116
3 2026-08-26 00:37 639233005922655772
1077 ms 202.69.36.116
2 2026-08-26 00:20 639232995672256907
745 ms 202.69.36.116
1 2026-08-26 00:03 639232985300872416
741 ms 202.69.36.116