DNS response history for b.nsangler.net

b.nsangler.net 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 530 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 b.nsangler.net.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

530 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.212.92.232

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 b.nsangler.net

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:39 639233403515141099
275 ms 49.212.92.232
34 2026-08-26 10:45 639233370841350248
551 ms 49.212.92.232
33 2026-08-26 10:28 639233360361507238
539 ms 49.212.92.232
32 2026-08-26 10:10 639233350067824371
551 ms 49.212.92.232
31 2026-08-26 09:53 639233339545274518
539 ms 49.212.92.232
30 2026-08-26 09:35 639233329214918079
521 ms 49.212.92.232
29 2026-08-26 09:18 639233318749762337
537 ms 49.212.92.232
28 2026-08-26 09:01 639233308387917838
559 ms 49.212.92.232
27 2026-08-26 08:44 639233297961740122
557 ms 49.212.92.232
26 2026-08-26 08:26 639233287487159094
542 ms 49.212.92.232
25 2026-08-26 08:09 639233276995531707
548 ms 49.212.92.232
24 2026-08-26 07:51 639233266521568229
274 ms 49.212.92.232
23 2026-08-26 07:34 639233256081047431
286 ms 49.212.92.232
22 2026-08-26 06:40 639233223620132921
279 ms 49.212.92.232
21 2026-08-26 06:22 639233213287814244
3 ms 49.212.92.232
20 2026-08-26 06:05 639233202925983161
558 ms 49.212.92.232
19 2026-08-26 05:48 639233192644780696
280 ms 49.212.92.232
18 2026-08-26 05:31 639233182401183833
551 ms 49.212.92.232
17 2026-08-26 05:14 639233172074181051
286 ms 49.212.92.232
16 2026-08-26 04:56 639233161808421455
559 ms 49.212.92.232
15 2026-08-26 04:39 639233151357344052
545 ms 49.212.92.232
14 2026-08-26 04:22 639233141034116946
6 ms 49.212.92.232
13 2026-08-26 04:05 639233130828334142
4 ms 49.212.92.232
12 2026-08-26 03:48 639233120373450007
567 ms 49.212.92.232
11 2026-08-26 03:30 639233110066216193
556 ms 49.212.92.232
10 2026-08-26 02:37 639233078065410564
6 ms 49.212.92.232
9 2026-08-26 02:20 639233067787457832
527 ms 49.212.92.232
8 2026-08-26 02:03 639233057501801162
542 ms 49.212.92.232
7 2026-08-26 01:46 639233047089431703
2310 ms 49.212.92.232
6 2026-08-26 01:28 639233036754790688
2273 ms 49.212.92.232
5 2026-08-26 01:11 639233026412602472
552 ms 49.212.92.232
4 2026-08-26 00:54 639233016064066127
521 ms 49.212.92.232
3 2026-08-26 00:37 639233005922655772
538 ms 49.212.92.232
2 2026-08-26 00:20 639232995672256907
270 ms 49.212.92.232
1 2026-08-26 00:02 639232985300872416
536 ms 49.212.92.232