DNS response history for ns1.oobben.info

ns1.oobben.info 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 227 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.oobben.info.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

227 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.29.136.23

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.oobben.info

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 09:47 639232471861770303
320 ms 66.29.136.23
28 2026-08-25 09:30 639232461630217327
317 ms 66.29.136.23
27 2026-08-25 09:13 639232451282965990
164 ms 66.29.136.23
26 2026-08-25 08:56 639232440814614938
312 ms 66.29.136.23
25 2026-08-25 08:38 639232430410720425
337 ms 66.29.136.23
24 2026-08-25 08:21 639232420003096185
417 ms 66.29.136.23
23 2026-08-25 08:04 639232409467287444
324 ms 66.29.136.23
22 2026-08-25 07:46 639232399077195997
437 ms 66.29.136.23
21 2026-08-25 07:29 639232388731528337
325 ms 66.29.136.23
20 2026-08-25 07:11 639232378288598612
445 ms 66.29.136.23
19 2026-08-25 06:18 639232346196373643
2 ms 66.29.136.23
18 2026-08-25 06:01 639232336112370741
332 ms 66.29.136.23
17 2026-08-25 05:44 639232326146508970
2 ms 66.29.136.23
16 2026-08-25 05:27 639232316189381720
3 ms 66.29.136.23
15 2026-08-25 05:11 639232306217998913
14 ms 66.29.136.23
14 2026-08-25 04:54 639232296255744174
313 ms 66.29.136.23
13 2026-08-25 04:38 639232286095760789
4 ms 66.29.136.23
12 2026-08-25 04:21 639232276086186273
157 ms 66.29.136.23
11 2026-08-25 04:04 639232265900986425
152 ms 66.29.136.23
10 2026-08-25 03:47 639232255723518075
152 ms 66.29.136.23
9 2026-08-25 03:30 639232245484452890
152 ms 66.29.136.23
8 2026-08-25 03:13 639232235157175331
158 ms 66.29.136.23
7 2026-08-25 02:19 639232203197189095
155 ms 66.29.136.23
6 2026-08-25 02:02 639232192844564298
317 ms 66.29.136.23
5 2026-08-25 01:45 639232182496008942
319 ms 66.29.136.23
4 2026-08-25 01:28 639232172197053132
314 ms 66.29.136.23
3 2026-08-25 00:34 639232140250307418
3 ms 66.29.136.23
2 2026-08-25 00:18 639232129927860324
314 ms 66.29.136.23
1 2026-08-25 00:00 639232119551972438
322 ms 66.29.136.23