DNS response history for ns3.21tb.com

ns3.21tb.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 34 DNS check records, 34 successful responses, 0 failed responses, and 498 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 ns3.21tb.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

498 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

47.84.45.240

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns3.21tb.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
34 2026-08-26 10:44 639233370841350248
506 ms 47.84.45.240
33 2026-08-26 10:27 639233360361507238
2488 ms 47.84.45.240
32 2026-08-26 10:10 639233350067824371
236 ms 47.84.45.240
31 2026-08-26 09:53 639233339545274518
399 ms 47.84.45.240
30 2026-08-26 09:35 639233329214918079
483 ms 47.84.45.240
29 2026-08-26 09:18 639233318749762337
233 ms 47.84.45.240
28 2026-08-26 09:00 639233308387917838
241 ms 47.84.45.240
27 2026-08-26 08:43 639233297961740122
236 ms 47.84.45.240
26 2026-08-26 08:26 639233287487159094
475 ms 47.84.45.240
25 2026-08-26 08:08 639233276995531707
504 ms 47.84.45.240
24 2026-08-26 07:51 639233266521568229
510 ms 47.84.45.240
23 2026-08-26 07:33 639233256081047431
250 ms 47.84.45.240
22 2026-08-26 06:39 639233223620132921
237 ms 47.84.45.240
21 2026-08-26 06:22 639233213287814244
2322 ms 47.84.45.240
20 2026-08-26 06:05 639233202925983161
234 ms 47.84.45.240
19 2026-08-26 05:47 639233192644780696
233 ms 47.84.45.240
18 2026-08-26 05:30 639233182401183833
244 ms 47.84.45.240
17 2026-08-26 05:13 639233172074181051
241 ms 47.84.45.240
16 2026-08-26 04:56 639233161808421455
241 ms 47.84.45.240
15 2026-08-26 04:39 639233151357344052
233 ms 47.84.45.240
14 2026-08-26 04:21 639233141034116946
246 ms 47.84.45.240
13 2026-08-26 04:04 639233130828334142
246 ms 47.84.45.240
12 2026-08-26 03:47 639233120373450007
231 ms 47.84.45.240
11 2026-08-26 03:30 639233110066216193
481 ms 47.84.45.240
10 2026-08-26 02:37 639233078065410564
462 ms 47.84.45.240
9 2026-08-26 02:19 639233067787457832
489 ms 47.84.45.240
8 2026-08-26 02:02 639233057501801162
237 ms 47.84.45.240
7 2026-08-26 01:45 639233047089431703
2444 ms 47.84.45.240
6 2026-08-26 01:28 639233036754790688
374 ms 47.84.45.240
5 2026-08-26 01:11 639233026412602472
239 ms 47.84.45.240
4 2026-08-26 00:53 639233016064066127
236 ms 47.84.45.240
3 2026-08-26 00:36 639233005922655772
244 ms 47.84.45.240
2 2026-08-26 00:19 639232995672256907
237 ms 47.84.45.240
1 2026-08-26 00:02 639232985300872416
236 ms 47.84.45.240