DNS response history for n2.doregi.com

n2.doregi.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 37 DNS check records, 37 successful responses, 0 failed responses, and 334 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 n2.doregi.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

334 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

121.78.117.39

Most recently resolved hosting IP on selected date

Successful Responses

37

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 n2.doregi.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
37 2026-08-25 12:57 639232587225721862
258 ms 121.78.117.39
36 2026-08-25 12:40 639232576780683689
300 ms 121.78.117.39
35 2026-08-25 12:22 639232566381512620
297 ms 121.78.117.39
34 2026-08-25 12:05 639232556111768563
285 ms 121.78.117.39
33 2026-08-25 11:48 639232545839529039
344 ms 121.78.117.39
32 2026-08-25 11:31 639232535349285207
286 ms 121.78.117.39
31 2026-08-25 11:13 639232524938080723
252 ms 121.78.117.39
30 2026-08-25 10:19 639232492740373468
256 ms 121.78.117.39
29 2026-08-25 10:02 639232482235303141
255 ms 121.78.117.39
28 2026-08-25 09:45 639232471861770303
301 ms 121.78.117.39
27 2026-08-25 09:27 639232461630217327
257 ms 121.78.117.39
26 2026-08-25 09:10 639232451282965990
294 ms 121.78.117.39
25 2026-08-25 08:53 639232440814614938
293 ms 121.78.117.39
24 2026-08-25 08:36 639232430410720425
290 ms 121.78.117.39
23 2026-08-25 08:18 639232420003096185
288 ms 121.78.117.39
22 2026-08-25 08:01 639232409467287444
262 ms 121.78.117.39
21 2026-08-25 07:43 639232399077195997
262 ms 121.78.117.39
20 2026-08-25 07:26 639232388731528337
263 ms 121.78.117.39
19 2026-08-25 07:09 639232378288598612
291 ms 121.78.117.39
18 2026-08-25 06:15 639232346196373643
575 ms 121.78.117.39
17 2026-08-25 05:58 639232336112370741
286 ms 121.78.117.39
16 2026-08-25 05:42 639232326146508970
265 ms 121.78.117.39
15 2026-08-25 05:25 639232316189381720
279 ms 121.78.117.39
14 2026-08-25 05:08 639232306217998913
294 ms 121.78.117.39
13 2026-08-25 04:52 639232296255744174
4 ms 121.78.117.39
12 2026-08-25 04:35 639232286095760789
265 ms 121.78.117.39
11 2026-08-25 04:18 639232276086186273
304 ms 121.78.117.39
10 2026-08-25 04:01 639232265900986425
284 ms 121.78.117.39
9 2026-08-25 03:44 639232255723518075
263 ms 121.78.117.39
8 2026-08-25 03:27 639232245484452890
2287 ms 121.78.117.39
7 2026-08-25 03:10 639232235157175331
265 ms 121.78.117.39
6 2026-08-25 02:17 639232203197189095
283 ms 121.78.117.39
5 2026-08-25 02:00 639232192844564298
288 ms 121.78.117.39
4 2026-08-25 01:42 639232182496008942
257 ms 121.78.117.39
3 2026-08-25 01:25 639232172197053132
264 ms 121.78.117.39
2 2026-08-25 00:32 639232140250307418
256 ms 121.78.117.39
1 2026-08-25 00:15 639232129927860324
294 ms 121.78.117.39