DNS response history for ns3.bitrangetech.com

ns3.bitrangetech.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-27. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 368 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.bitrangetech.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

368 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

96.69.156.53

Most recently resolved hosting IP on selected date

Successful Responses

36

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

Showing DNS history for 2026-08-27 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
36 2026-08-27 12:07 639234286253196126
279 ms 96.69.156.53
35 2026-08-27 11:14 639234253963286387
134 ms 96.69.156.53
34 2026-08-27 10:56 639234243654907465
279 ms 96.69.156.53
33 2026-08-27 10:39 639234233269654413
277 ms 96.69.156.53
32 2026-08-27 10:22 639234222943951923
2149 ms 96.69.156.53
31 2026-08-27 10:05 639234212558002823
283 ms 96.69.156.53
30 2026-08-27 09:47 639234202117531850
276 ms 96.69.156.53
29 2026-08-27 09:30 639234191649612722
289 ms 96.69.156.53
28 2026-08-27 09:12 639234181105879568
278 ms 96.69.156.53
27 2026-08-27 08:55 639234170713214496
278 ms 96.69.156.53
26 2026-08-27 08:38 639234160341037652
278 ms 96.69.156.53
25 2026-08-27 08:20 639234149799404224
276 ms 96.69.156.53
24 2026-08-27 08:03 639234139553286469
279 ms 96.69.156.53
23 2026-08-27 07:09 639234107183588293
276 ms 96.69.156.53
22 2026-08-27 06:52 639234096905435724
280 ms 96.69.156.53
21 2026-08-27 06:35 639234086579410775
275 ms 96.69.156.53
20 2026-08-27 06:17 639234076291157956
274 ms 96.69.156.53
19 2026-08-27 06:00 639234065981939454
283 ms 96.69.156.53
18 2026-08-27 05:43 639234055548642997
276 ms 96.69.156.53
17 2026-08-27 05:26 639234045267979603
2148 ms 96.69.156.53
16 2026-08-27 05:09 639234034999717463
277 ms 96.69.156.53
15 2026-08-27 04:52 639234024739225358
299 ms 96.69.156.53
14 2026-08-27 04:34 639234014311170162
251 ms 96.69.156.53
13 2026-08-27 04:17 639234003806017640
277 ms 96.69.156.53
12 2026-08-27 03:59 639233993356203030
285 ms 96.69.156.53
11 2026-08-27 03:06 639233961301716608
277 ms 96.69.156.53
10 2026-08-27 02:49 639233950834200647
294 ms 96.69.156.53
9 2026-08-27 02:31 639233940431849026
135 ms 96.69.156.53
8 2026-08-27 02:14 639233930110596398
277 ms 96.69.156.53
7 2026-08-27 01:57 639233919705434540
170 ms 96.69.156.53
6 2026-08-27 01:40 639233909452807845
136 ms 96.69.156.53
5 2026-08-27 01:22 639233899096420820
274 ms 96.69.156.53
4 2026-08-27 01:05 639233888707824939
293 ms 96.69.156.53
3 2026-08-27 00:48 639233878461203802
278 ms 96.69.156.53
2 2026-08-27 00:31 639233868060868209
275 ms 96.69.156.53
1 2026-08-27 00:13 639233857450922991
286 ms 96.69.156.53