DNS response history for ns2.longforce.com

ns2.longforce.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 35 DNS check records, 35 successful responses, 0 failed responses, and 400 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.longforce.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

400 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

122.193.90.242

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 ns2.longforce.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
35 2026-08-24 15:03 639231797631669865
3 ms 122.193.90.242
34 2026-08-24 14:10 639231765923559455
2007 ms 122.193.90.242
33 2026-08-24 13:53 639231755868832964
543 ms 122.193.90.242
32 2026-08-24 13:36 639231745628278877
514 ms 122.193.90.242
31 2026-08-24 13:19 639231735407682062
2271 ms 122.193.90.242
30 2026-08-24 12:26 639231703815441688
5 ms 122.193.90.242
29 2026-08-24 12:09 639231693747052549
5 ms 122.193.90.242
28 2026-08-24 11:52 639231683712487276
4 ms 122.193.90.242
27 2026-08-24 11:36 639231673513573868
4 ms 122.193.90.242
26 2026-08-24 10:42 639231641791249939
942 ms 122.193.90.242
25 2026-08-24 10:26 639231631866211033
3 ms 122.193.90.242
24 2026-08-24 10:09 639231621644955316
13 ms 122.193.90.242
23 2026-08-24 09:52 639231611478799259
497 ms 122.193.90.242
22 2026-08-24 09:00 639231579923718211
3 ms 122.193.90.242
21 2026-08-24 08:43 639231569810702936
580 ms 122.193.90.242
20 2026-08-24 08:26 639231559762411619
2 ms 122.193.90.242
19 2026-08-24 08:09 639231549663595407
2 ms 122.193.90.242
18 2026-08-24 07:16 639231518076817246
527 ms 122.193.90.242
17 2026-08-24 07:00 639231508078650885
4 ms 122.193.90.242
16 2026-08-24 06:43 639231498210697093
535 ms 122.193.90.242
15 2026-08-24 06:27 639231488109699360
593 ms 122.193.90.242
14 2026-08-24 05:34 639231456772510692
2375 ms 122.193.90.242
13 2026-08-24 05:18 639231447084631185
3 ms 122.193.90.242
12 2026-08-24 05:01 639231437208519473
3 ms 122.193.90.242
11 2026-08-24 04:45 639231427209627490
2 ms 122.193.90.242
10 2026-08-24 03:52 639231395791246644
578 ms 122.193.90.242
9 2026-08-24 03:36 639231386075551458
313 ms 122.193.90.242
8 2026-08-24 03:20 639231376208713791
252 ms 122.193.90.242
7 2026-08-24 03:03 639231366170589276
3 ms 122.193.90.242
6 2026-08-24 02:11 639231334732159368
3 ms 122.193.90.242
5 2026-08-24 01:54 639231325035670078
3 ms 122.193.90.242
4 2026-08-24 01:38 639231315132253837
3 ms 122.193.90.242
3 2026-08-24 01:22 639231305014280808
293 ms 122.193.90.242
2 2026-08-24 00:29 639231273779380675
553 ms 122.193.90.242
1 2026-08-24 00:13 639231264180839154
570 ms 122.193.90.242