DNS response history for ns1.e-yamato.news

ns1.e-yamato.news 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 36 DNS check records, 36 successful responses, 0 failed responses, and 501 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.e-yamato.news.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

501 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

39.110.231.213

Most recently resolved hosting IP on selected date

Successful Responses

36

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.e-yamato.news

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
36 2026-08-27 12:08 639234286253196126
237 ms 39.110.231.213
35 2026-08-27 11:14 639234253963286387
622 ms 39.110.231.213
34 2026-08-27 10:57 639234243654907465
220 ms 39.110.231.213
33 2026-08-27 10:40 639234233269654413
562 ms 39.110.231.213
32 2026-08-27 10:23 639234222943951923
579 ms 39.110.231.213
31 2026-08-27 10:05 639234212558002823
459 ms 39.110.231.213
30 2026-08-27 09:48 639234202117531850
450 ms 39.110.231.213
29 2026-08-27 09:30 639234191649612722
227 ms 39.110.231.213
28 2026-08-27 09:13 639234181105879568
457 ms 39.110.231.213
27 2026-08-27 08:55 639234170713214496
449 ms 39.110.231.213
26 2026-08-27 08:38 639234160341037652
461 ms 39.110.231.213
25 2026-08-27 08:21 639234149799404224
467 ms 39.110.231.213
24 2026-08-27 08:03 639234139553286469
472 ms 39.110.231.213
23 2026-08-27 07:10 639234107183588293
231 ms 39.110.231.213
22 2026-08-27 06:52 639234096905435724
452 ms 39.110.231.213
21 2026-08-27 06:35 639234086579410775
221 ms 39.110.231.213
20 2026-08-27 06:18 639234076291157956
219 ms 39.110.231.213
19 2026-08-27 06:01 639234065981939454
7 ms 39.110.231.213
18 2026-08-27 05:44 639234055548642997
456 ms 39.110.231.213
17 2026-08-27 05:26 639234045267979603
380 ms 39.110.231.213
16 2026-08-27 05:09 639234034999717463
566 ms 39.110.231.213
15 2026-08-27 04:52 639234024739225358
2031 ms 39.110.231.213
14 2026-08-27 04:35 639234014311170162
238 ms 39.110.231.213
13 2026-08-27 04:17 639234003806017640
675 ms 39.110.231.213
12 2026-08-27 04:00 639233993356203030
456 ms 39.110.231.213
11 2026-08-27 03:07 639233961301716608
218 ms 39.110.231.213
10 2026-08-27 02:49 639233950834200647
466 ms 39.110.231.213
9 2026-08-27 02:32 639233940431849026
715 ms 39.110.231.213
8 2026-08-27 02:15 639233930110596398
241 ms 39.110.231.213
7 2026-08-27 01:57 639233919705434540
2007 ms 39.110.231.213
6 2026-08-27 01:40 639233909452807845
598 ms 39.110.231.213
5 2026-08-27 01:23 639233899096420820
558 ms 39.110.231.213
4 2026-08-27 01:06 639233888707824939
565 ms 39.110.231.213
3 2026-08-27 00:48 639233878461203802
33 ms 39.110.231.213
2 2026-08-27 00:31 639233868060868209
461 ms 39.110.231.213
1 2026-08-27 00:14 639233857450922991
579 ms 39.110.231.213