DNS response history for ns1.sailingscores.com

ns1.sailingscores.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 34 DNS check records, 34 successful responses, 0 failed responses, and 311 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.sailingscores.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

311 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

167.99.120.83

Most recently resolved hosting IP on selected date

Successful Responses

34

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.sailingscores.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
34 2026-08-25 12:03 639232556111768563
275 ms 167.99.120.83
33 2026-08-25 11:46 639232545839529039
269 ms 167.99.120.83
32 2026-08-25 11:29 639232535349285207
268 ms 167.99.120.83
31 2026-08-25 11:11 639232524938080723
273 ms 167.99.120.83
30 2026-08-25 10:18 639232492740373468
2010 ms 167.99.120.83
29 2026-08-25 10:01 639232482235303141
161 ms 167.99.120.83
28 2026-08-25 09:43 639232471861770303
286 ms 167.99.120.83
27 2026-08-25 09:26 639232461630217327
290 ms 167.99.120.83
26 2026-08-25 09:09 639232451282965990
2010 ms 167.99.120.83
25 2026-08-25 08:51 639232440814614938
273 ms 167.99.120.83
24 2026-08-25 08:34 639232430410720425
290 ms 167.99.120.83
23 2026-08-25 08:17 639232420003096185
270 ms 167.99.120.83
22 2026-08-25 07:59 639232409467287444
278 ms 167.99.120.83
21 2026-08-25 07:42 639232399077195997
283 ms 167.99.120.83
20 2026-08-25 07:24 639232388731528337
126 ms 167.99.120.83
19 2026-08-25 07:07 639232378288598612
287 ms 167.99.120.83
18 2026-08-25 06:13 639232346196373643
108 ms 167.99.120.83
17 2026-08-25 05:56 639232336112370741
289 ms 167.99.120.83
16 2026-08-25 05:40 639232326146508970
160 ms 167.99.120.83
15 2026-08-25 05:23 639232316189381720
300 ms 167.99.120.83
14 2026-08-25 05:07 639232306217998913
4 ms 167.99.120.83
13 2026-08-25 04:50 639232296255744174
5 ms 167.99.120.83
12 2026-08-25 04:33 639232286095760789
279 ms 167.99.120.83
11 2026-08-25 04:16 639232276086186273
4 ms 167.99.120.83
10 2026-08-25 04:00 639232265900986425
277 ms 167.99.120.83
9 2026-08-25 03:43 639232255723518075
3 ms 167.99.120.83
8 2026-08-25 03:26 639232245484452890
271 ms 167.99.120.83
7 2026-08-25 03:08 639232235157175331
278 ms 167.99.120.83
6 2026-08-25 02:15 639232203197189095
3 ms 167.99.120.83
5 2026-08-25 01:58 639232192844564298
102 ms 167.99.120.83
4 2026-08-25 01:41 639232182496008942
269 ms 167.99.120.83
3 2026-08-25 01:23 639232172197053132
270 ms 167.99.120.83
2 2026-08-25 00:30 639232140250307418
285 ms 167.99.120.83
1 2026-08-25 00:13 639232129927860324
3 ms 167.99.120.83