DNS response history for ns.oops.org

ns.oops.org 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 32 DNS check records, 32 successful responses, 0 failed responses, and 596 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 ns.oops.org.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

596 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.117.209.99

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 ns.oops.org

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
32 2026-08-25 11:15 639232524938080723
535 ms 210.117.209.99
31 2026-08-25 10:22 639232492740373468
387 ms 210.117.209.99
30 2026-08-25 10:05 639232482235303141
531 ms 210.117.209.99
29 2026-08-25 09:47 639232471861770303
530 ms 210.117.209.99
28 2026-08-25 09:30 639232461630217327
529 ms 210.117.209.99
27 2026-08-25 09:13 639232451282965990
552 ms 210.117.209.99
26 2026-08-25 08:55 639232440814614938
525 ms 210.117.209.99
25 2026-08-25 08:38 639232430410720425
507 ms 210.117.209.99
24 2026-08-25 08:21 639232420003096185
753 ms 210.117.209.99
23 2026-08-25 08:03 639232409467287444
528 ms 210.117.209.99
22 2026-08-25 07:46 639232399077195997
643 ms 210.117.209.99
21 2026-08-25 07:28 639232388731528337
2277 ms 210.117.209.99
20 2026-08-25 07:11 639232378288598612
647 ms 210.117.209.99
19 2026-08-25 06:17 639232346196373643
515 ms 210.117.209.99
18 2026-08-25 06:00 639232336112370741
651 ms 210.117.209.99
17 2026-08-25 05:44 639232326146508970
635 ms 210.117.209.99
16 2026-08-25 05:27 639232316189381720
526 ms 210.117.209.99
15 2026-08-25 05:11 639232306217998913
528 ms 210.117.209.99
14 2026-08-25 04:54 639232296255744174
523 ms 210.117.209.99
13 2026-08-25 04:37 639232286095760789
514 ms 210.117.209.99
12 2026-08-25 04:20 639232276086186273
518 ms 210.117.209.99
11 2026-08-25 04:04 639232265900986425
515 ms 210.117.209.99
10 2026-08-25 03:47 639232255723518075
514 ms 210.117.209.99
9 2026-08-25 03:30 639232245484452890
527 ms 210.117.209.99
8 2026-08-25 03:12 639232235157175331
529 ms 210.117.209.99
7 2026-08-25 02:19 639232203197189095
513 ms 210.117.209.99
6 2026-08-25 02:02 639232192844564298
525 ms 210.117.209.99
5 2026-08-25 01:45 639232182496008942
531 ms 210.117.209.99
4 2026-08-25 01:27 639232172197053132
528 ms 210.117.209.99
3 2026-08-25 00:34 639232140250307418
505 ms 210.117.209.99
2 2026-08-25 00:17 639232129927860324
516 ms 210.117.209.99
1 2026-08-25 00:00 639232119551972438
518 ms 210.117.209.99