DNS response history for ns2.oryzentech.com

ns2.oryzentech.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 33 DNS check records, 33 successful responses, 0 failed responses, and 650 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 ns2.oryzentech.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

650 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

109.199.99.122

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns2.oryzentech.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
33 2026-08-25 11:39 639232545839529039
2025 ms 109.199.99.122
32 2026-08-25 11:22 639232535349285207
2018 ms 109.199.99.122
31 2026-08-25 11:04 639232524938080723
41 ms 109.199.99.122
30 2026-08-25 10:11 639232492740373468
43 ms 109.199.99.122
29 2026-08-25 09:53 639232482235303141
11 ms 109.199.99.122
28 2026-08-25 09:36 639232471861770303
36 ms 109.199.99.122
27 2026-08-25 09:19 639232461630217327
44 ms 109.199.99.122
26 2026-08-25 09:01 639232451282965990
2029 ms 109.199.99.122
25 2026-08-25 08:44 639232440814614938
154 ms 109.199.99.122
24 2026-08-25 08:27 639232430410720425
53 ms 109.199.99.122
23 2026-08-25 08:09 639232420003096185
2045 ms 109.199.99.122
22 2026-08-25 07:52 639232409467287444
57 ms 109.199.99.122
21 2026-08-25 07:34 639232399077195997
2035 ms 109.199.99.122
20 2026-08-25 07:17 639232388731528337
7 ms 109.199.99.122
19 2026-08-25 07:00 639232378288598612
48 ms 109.199.99.122
18 2026-08-25 06:06 639232346196373643
33 ms 109.199.99.122
17 2026-08-25 05:49 639232336112370741
36 ms 109.199.99.122
16 2026-08-25 05:33 639232326146508970
50 ms 109.199.99.122
15 2026-08-25 05:16 639232316189381720
34 ms 109.199.99.122
14 2026-08-25 05:00 639232306217998913
13 ms 109.199.99.122
13 2026-08-25 04:43 639232296255744174
54 ms 109.199.99.122
12 2026-08-25 04:26 639232286095760789
38 ms 109.199.99.122
11 2026-08-25 04:09 639232276086186273
71 ms 109.199.99.122
10 2026-08-25 03:53 639232265900986425
2038 ms 109.199.99.122
9 2026-08-25 03:36 639232255723518075
4020 ms 109.199.99.122
8 2026-08-25 03:18 639232245484452890
55 ms 109.199.99.122
7 2026-08-25 03:01 639232235157175331
2036 ms 109.199.99.122
6 2026-08-25 02:08 639232203197189095
35 ms 109.199.99.122
5 2026-08-25 01:51 639232192844564298
72 ms 109.199.99.122
4 2026-08-25 01:34 639232182496008942
2071 ms 109.199.99.122
3 2026-08-25 01:16 639232172197053132
50 ms 109.199.99.122
2 2026-08-25 00:23 639232140250307418
67 ms 109.199.99.122
1 2026-08-25 00:06 639232129927860324
37 ms 109.199.99.122