DNS response history for s4.latitudeonedallas.com

s4.latitudeonedallas.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-27. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 348 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 s4.latitudeonedallas.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

348 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.38.142.157

Most recently resolved hosting IP on selected date

Successful Responses

32

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 s4.latitudeonedallas.com

Showing DNS history for 2026-08-27 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
32 2026-08-27 10:22 639234222943951923
149 ms 51.38.142.157
31 2026-08-27 10:04 639234212558002823
15 ms 51.38.142.157
30 2026-08-27 09:47 639234202117531850
269 ms 51.38.142.157
29 2026-08-27 09:29 639234191649612722
217 ms 51.38.142.157
28 2026-08-27 09:12 639234181105879568
120 ms 51.38.142.157
27 2026-08-27 08:54 639234170713214496
207 ms 51.38.142.157
26 2026-08-27 08:37 639234160341037652
7 ms 51.38.142.157
25 2026-08-27 08:20 639234149799404224
225 ms 51.38.142.157
24 2026-08-27 08:02 639234139553286469
41 ms 51.38.142.157
23 2026-08-27 07:09 639234107183588293
136 ms 51.38.142.157
22 2026-08-27 06:51 639234096905435724
217 ms 51.38.142.157
21 2026-08-27 06:34 639234086579410775
108 ms 51.38.142.157
20 2026-08-27 06:17 639234076291157956
226 ms 51.38.142.157
19 2026-08-27 06:00 639234065981939454
234 ms 51.38.142.157
18 2026-08-27 05:43 639234055548642997
9 ms 51.38.142.157
17 2026-08-27 05:25 639234045267979603
215 ms 51.38.142.157
16 2026-08-27 05:08 639234034999717463
106 ms 51.38.142.157
15 2026-08-27 04:51 639234024739225358
219 ms 51.38.142.157
14 2026-08-27 04:34 639234014311170162
214 ms 51.38.142.157
13 2026-08-27 04:17 639234003806017640
2007 ms 51.38.142.157
12 2026-08-27 03:59 639233993356203030
2165 ms 51.38.142.157
11 2026-08-27 03:06 639233961301716608
209 ms 51.38.142.157
10 2026-08-27 02:48 639233950834200647
147 ms 51.38.142.157
9 2026-08-27 02:31 639233940431849026
213 ms 51.38.142.157
8 2026-08-27 02:14 639233930110596398
2009 ms 51.38.142.157
7 2026-08-27 01:56 639233919705434540
206 ms 51.38.142.157
6 2026-08-27 01:39 639233909452807845
209 ms 51.38.142.157
5 2026-08-27 01:22 639233899096420820
212 ms 51.38.142.157
4 2026-08-27 01:05 639233888707824939
283 ms 51.38.142.157
3 2026-08-27 00:47 639233878461203802
109 ms 51.38.142.157
2 2026-08-27 00:30 639233868060868209
214 ms 51.38.142.157
1 2026-08-27 00:13 639233857450922991
219 ms 51.38.142.157