DNS response history for ns1.jetforcehost.com

ns1.jetforcehost.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-25. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 323 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 ns1.jetforcehost.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

323 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

165.140.71.65

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns1.jetforcehost.com

Showing DNS history for 2026-08-25 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
29 2026-08-25 10:02 639232482235303141
244 ms 165.140.71.65
28 2026-08-25 09:44 639232471861770303
144 ms 165.140.71.65
27 2026-08-25 09:27 639232461630217327
118 ms 165.140.71.65
26 2026-08-25 09:10 639232451282965990
579 ms 165.140.71.65
25 2026-08-25 08:52 639232440814614938
9 ms 165.140.71.65
24 2026-08-25 08:35 639232430410720425
239 ms 165.140.71.65
23 2026-08-25 08:18 639232420003096185
21 ms 165.140.71.65
22 2026-08-25 08:00 639232409467287444
4 ms 165.140.71.65
21 2026-08-25 07:43 639232399077195997
2147 ms 165.140.71.65
20 2026-08-25 07:25 639232388731528337
265 ms 165.140.71.65
19 2026-08-25 07:08 639232378288598612
269 ms 165.140.71.65
18 2026-08-25 06:14 639232346196373643
118 ms 165.140.71.65
17 2026-08-25 05:57 639232336112370741
245 ms 165.140.71.65
16 2026-08-25 05:41 639232326146508970
239 ms 165.140.71.65
15 2026-08-25 05:24 639232316189381720
240 ms 165.140.71.65
14 2026-08-25 05:08 639232306217998913
2135 ms 165.140.71.65
13 2026-08-25 04:51 639232296255744174
127 ms 165.140.71.65
12 2026-08-25 04:34 639232286095760789
4 ms 165.140.71.65
11 2026-08-25 04:17 639232276086186273
245 ms 165.140.71.65
10 2026-08-25 04:01 639232265900986425
244 ms 165.140.71.65
9 2026-08-25 03:44 639232255723518075
121 ms 165.140.71.65
8 2026-08-25 03:27 639232245484452890
244 ms 165.140.71.65
7 2026-08-25 03:09 639232235157175331
142 ms 165.140.71.65
6 2026-08-25 02:16 639232203197189095
4 ms 165.140.71.65
5 2026-08-25 01:59 639232192844564298
239 ms 165.140.71.65
4 2026-08-25 01:42 639232182496008942
260 ms 165.140.71.65
3 2026-08-25 01:24 639232172197053132
235 ms 165.140.71.65
2 2026-08-25 00:31 639232140250307418
236 ms 165.140.71.65
1 2026-08-25 00:14 639232129927860324
237 ms 165.140.71.65