DNS response history for ns2.ngabay.com

ns2.ngabay.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-24. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 376 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.ngabay.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

376 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.79.249.193

Most recently resolved hosting IP on selected date

Successful Responses

26

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

Showing DNS history for 2026-08-24 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
26 2026-08-24 10:41 639231641791249939
3 ms 51.79.249.193
25 2026-08-24 10:25 639231631866211033
331 ms 51.79.249.193
24 2026-08-24 10:08 639231621644955316
339 ms 51.79.249.193
23 2026-08-24 09:51 639231611478799259
345 ms 51.79.249.193
22 2026-08-24 08:58 639231579923718211
240 ms 51.79.249.193
21 2026-08-24 08:41 639231569810702936
352 ms 51.79.249.193
20 2026-08-24 08:24 639231559762411619
416 ms 51.79.249.193
19 2026-08-24 08:08 639231549663595407
325 ms 51.79.249.193
18 2026-08-24 07:15 639231518076817246
254 ms 51.79.249.193
17 2026-08-24 06:59 639231508078650885
340 ms 51.79.249.193
16 2026-08-24 06:42 639231498210697093
325 ms 51.79.249.193
15 2026-08-24 06:25 639231488109699360
2277 ms 51.79.249.193
14 2026-08-24 05:33 639231456772510692
4 ms 51.79.249.193
13 2026-08-24 05:17 639231447084631185
427 ms 51.79.249.193
12 2026-08-24 05:00 639231437208519473
2314 ms 51.79.249.193
11 2026-08-24 04:43 639231427209627490
27 ms 51.79.249.193
10 2026-08-24 03:51 639231395791246644
4 ms 51.79.249.193
9 2026-08-24 03:35 639231386075551458
3 ms 51.79.249.193
8 2026-08-24 03:19 639231376208713791
306 ms 51.79.249.193
7 2026-08-24 03:02 639231366170589276
323 ms 51.79.249.193
6 2026-08-24 02:09 639231334732159368
325 ms 51.79.249.193
5 2026-08-24 01:53 639231325035670078
2 ms 51.79.249.193
4 2026-08-24 01:37 639231315132253837
2 ms 51.79.249.193
3 2026-08-24 01:20 639231305014280808
492 ms 51.79.249.193
2 2026-08-24 00:28 639231273779380675
4 ms 51.79.249.193
1 2026-08-24 00:12 639231264180839154
7 ms 51.79.249.193