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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 399 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

35

Historical checks stored for this nameserver on selected date

Average Latency

399 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:15

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

35

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-27 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
35 2026-08-27 11:15 639234253963286387
235 ms 121.78.117.39
34 2026-08-27 10:58 639234243654907465
289 ms 121.78.117.39
33 2026-08-27 10:40 639234233269654413
281 ms 121.78.117.39
32 2026-08-27 10:23 639234222943951923
290 ms 121.78.117.39
31 2026-08-27 10:06 639234212558002823
257 ms 121.78.117.39
30 2026-08-27 09:48 639234202117531850
284 ms 121.78.117.39
29 2026-08-27 09:31 639234191649612722
255 ms 121.78.117.39
28 2026-08-27 09:14 639234181105879568
293 ms 121.78.117.39
27 2026-08-27 08:56 639234170713214496
281 ms 121.78.117.39
26 2026-08-27 08:39 639234160341037652
264 ms 121.78.117.39
25 2026-08-27 08:21 639234149799404224
263 ms 121.78.117.39
24 2026-08-27 08:04 639234139553286469
288 ms 121.78.117.39
23 2026-08-27 07:10 639234107183588293
292 ms 121.78.117.39
22 2026-08-27 06:53 639234096905435724
567 ms 121.78.117.39
21 2026-08-27 06:36 639234086579410775
288 ms 121.78.117.39
20 2026-08-27 06:19 639234076291157956
294 ms 121.78.117.39
19 2026-08-27 06:02 639234065981939454
261 ms 121.78.117.39
18 2026-08-27 05:44 639234055548642997
259 ms 121.78.117.39
17 2026-08-27 05:27 639234045267979603
286 ms 121.78.117.39
16 2026-08-27 05:10 639234034999717463
286 ms 121.78.117.39
15 2026-08-27 04:53 639234024739225358
290 ms 121.78.117.39
14 2026-08-27 04:36 639234014311170162
294 ms 121.78.117.39
13 2026-08-27 04:18 639234003806017640
284 ms 121.78.117.39
12 2026-08-27 04:00 639233993356203030
266 ms 121.78.117.39
11 2026-08-27 03:07 639233961301716608
288 ms 121.78.117.39
10 2026-08-27 02:50 639233950834200647
2266 ms 121.78.117.39
9 2026-08-27 02:32 639233940431849026
3 ms 121.78.117.39
8 2026-08-27 02:15 639233930110596398
2286 ms 121.78.117.39
7 2026-08-27 01:58 639233919705434540
285 ms 121.78.117.39
6 2026-08-27 01:41 639233909452807845
287 ms 121.78.117.39
5 2026-08-27 01:23 639233899096420820
255 ms 121.78.117.39
4 2026-08-27 01:06 639233888707824939
284 ms 121.78.117.39
3 2026-08-27 00:49 639233878461203802
517 ms 121.78.117.39
2 2026-08-27 00:32 639233868060868209
256 ms 121.78.117.39
1 2026-08-27 00:14 639233857450922991
279 ms 121.78.117.39