DNS response history for ns1.ridewide.net

ns1.ridewide.net 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 409 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.ridewide.net.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

409 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.141.41.37

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.ridewide.net

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 10:23 639232492740373468
296 ms 209.141.41.37
30 2026-08-25 10:06 639232482235303141
299 ms 209.141.41.37
29 2026-08-25 09:48 639232471861770303
5 ms 209.141.41.37
28 2026-08-25 09:31 639232461630217327
487 ms 209.141.41.37
27 2026-08-25 09:14 639232451282965990
317 ms 209.141.41.37
26 2026-08-25 08:56 639232440814614938
468 ms 209.141.41.37
25 2026-08-25 08:39 639232430410720425
303 ms 209.141.41.37
24 2026-08-25 08:22 639232420003096185
453 ms 209.141.41.37
23 2026-08-25 08:04 639232409467287444
459 ms 209.141.41.37
22 2026-08-25 07:47 639232399077195997
466 ms 209.141.41.37
21 2026-08-25 07:29 639232388731528337
451 ms 209.141.41.37
20 2026-08-25 07:12 639232378288598612
2160 ms 209.141.41.37
19 2026-08-25 06:18 639232346196373643
3 ms 209.141.41.37
18 2026-08-25 06:01 639232336112370741
449 ms 209.141.41.37
17 2026-08-25 05:45 639232326146508970
3 ms 209.141.41.37
16 2026-08-25 05:28 639232316189381720
4 ms 209.141.41.37
15 2026-08-25 05:12 639232306217998913
449 ms 209.141.41.37
14 2026-08-25 04:55 639232296255744174
298 ms 209.141.41.37
13 2026-08-25 04:38 639232286095760789
463 ms 209.141.41.37
12 2026-08-25 04:21 639232276086186273
298 ms 209.141.41.37
11 2026-08-25 04:05 639232265900986425
304 ms 209.141.41.37
10 2026-08-25 03:48 639232255723518075
494 ms 209.141.41.37
9 2026-08-25 03:31 639232245484452890
448 ms 209.141.41.37
8 2026-08-25 03:14 639232235157175331
449 ms 209.141.41.37
7 2026-08-25 02:20 639232203197189095
299 ms 209.141.41.37
6 2026-08-25 02:03 639232192844564298
447 ms 209.141.41.37
5 2026-08-25 01:46 639232182496008942
451 ms 209.141.41.37
4 2026-08-25 01:28 639232172197053132
448 ms 209.141.41.37
3 2026-08-25 00:35 639232140250307418
446 ms 209.141.41.37
2 2026-08-25 00:18 639232129927860324
458 ms 209.141.41.37
1 2026-08-25 00:01 639232119551972438
310 ms 209.141.41.37