DNS response history for ns2.nforce.com

ns2.nforce.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 260 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.nforce.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

260 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

77.247.176.115

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.nforce.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:31 639231641791249939
40 ms 77.247.176.115
25 2026-08-24 10:14 639231631866211033
34 ms 77.247.176.115
24 2026-08-24 09:57 639231621644955316
2046 ms 77.247.176.115
23 2026-08-24 09:40 639231611478799259
2080 ms 77.247.176.115
22 2026-08-24 08:48 639231579923718211
30 ms 77.247.176.115
21 2026-08-24 08:31 639231569810702936
21 ms 77.247.176.115
20 2026-08-24 08:14 639231559762411619
8 ms 77.247.176.115
19 2026-08-24 07:57 639231549663595407
34 ms 77.247.176.115
18 2026-08-24 07:05 639231518076817246
25 ms 77.247.176.115
17 2026-08-24 06:48 639231508078650885
3 ms 77.247.176.115
16 2026-08-24 06:32 639231498210697093
39 ms 77.247.176.115
15 2026-08-24 06:15 639231488109699360
26 ms 77.247.176.115
14 2026-08-24 05:23 639231456772510692
15 ms 77.247.176.115
13 2026-08-24 05:06 639231447084631185
2017 ms 77.247.176.115
12 2026-08-24 04:50 639231437208519473
34 ms 77.247.176.115
11 2026-08-24 04:33 639231427209627490
67 ms 77.247.176.115
10 2026-08-24 03:41 639231395791246644
30 ms 77.247.176.115
9 2026-08-24 03:25 639231386075551458
3 ms 77.247.176.115
8 2026-08-24 03:08 639231376208713791
26 ms 77.247.176.115
7 2026-08-24 02:52 639231366170589276
40 ms 77.247.176.115
6 2026-08-24 01:59 639231334732159368
11 ms 77.247.176.115
5 2026-08-24 01:43 639231325035670078
48 ms 77.247.176.115
4 2026-08-24 01:27 639231315132253837
22 ms 77.247.176.115
3 2026-08-24 01:10 639231305014280808
19 ms 77.247.176.115
2 2026-08-24 00:18 639231273779380675
40 ms 77.247.176.115
1 2026-08-24 00:02 639231264180839154
3 ms 77.247.176.115