DNS response history for ns1.richboroswimteam.com

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

31

Historical checks stored for this nameserver on selected date

Average Latency

292 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

160.153.172.160

Most recently resolved hosting IP on selected date

Successful Responses

31

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.richboroswimteam.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
31 2026-08-25 11:12 639232524938080723
340 ms 160.153.172.160
30 2026-08-25 10:18 639232492740373468
336 ms 160.153.172.160
29 2026-08-25 10:01 639232482235303141
7 ms 160.153.172.160
28 2026-08-25 09:44 639232471861770303
236 ms 160.153.172.160
27 2026-08-25 09:26 639232461630217327
4 ms 160.153.172.160
26 2026-08-25 09:09 639232451282965990
345 ms 160.153.172.160
25 2026-08-25 08:52 639232440814614938
342 ms 160.153.172.160
24 2026-08-25 08:34 639232430410720425
4 ms 160.153.172.160
23 2026-08-25 08:17 639232420003096185
212 ms 160.153.172.160
22 2026-08-25 08:00 639232409467287444
344 ms 160.153.172.160
21 2026-08-25 07:42 639232399077195997
348 ms 160.153.172.160
20 2026-08-25 07:25 639232388731528337
5 ms 160.153.172.160
19 2026-08-25 07:08 639232378288598612
353 ms 160.153.172.160
18 2026-08-25 06:14 639232346196373643
3 ms 160.153.172.160
17 2026-08-25 05:57 639232336112370741
10 ms 160.153.172.160
16 2026-08-25 05:41 639232326146508970
2236 ms 160.153.172.160
15 2026-08-25 05:24 639232316189381720
226 ms 160.153.172.160
14 2026-08-25 05:07 639232306217998913
341 ms 160.153.172.160
13 2026-08-25 04:51 639232296255744174
9 ms 160.153.172.160
12 2026-08-25 04:34 639232286095760789
333 ms 160.153.172.160
11 2026-08-25 04:17 639232276086186273
335 ms 160.153.172.160
10 2026-08-25 04:00 639232265900986425
341 ms 160.153.172.160
9 2026-08-25 03:43 639232255723518075
337 ms 160.153.172.160
8 2026-08-25 03:26 639232245484452890
195 ms 160.153.172.160
7 2026-08-25 03:09 639232235157175331
334 ms 160.153.172.160
6 2026-08-25 02:16 639232203197189095
355 ms 160.153.172.160
5 2026-08-25 01:59 639232192844564298
197 ms 160.153.172.160
4 2026-08-25 01:41 639232182496008942
7 ms 160.153.172.160
3 2026-08-25 01:24 639232172197053132
345 ms 160.153.172.160
2 2026-08-25 00:31 639232140250307418
352 ms 160.153.172.160
1 2026-08-25 00:14 639232129927860324
230 ms 160.153.172.160