DNS response history for ns.emi.kyoto

ns.emi.kyoto 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 38 DNS check records, 38 successful responses, 0 failed responses, and 547 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.emi.kyoto.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

547 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.122.96.111

Most recently resolved hosting IP on selected date

Successful Responses

38

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.emi.kyoto

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
38 2026-08-27 12:46 639234307007468133
546 ms 153.122.96.111
37 2026-08-27 12:28 639234296664302575
594 ms 153.122.96.111
36 2026-08-27 12:11 639234286253196126
545 ms 153.122.96.111
35 2026-08-27 11:17 639234253963286387
556 ms 153.122.96.111
34 2026-08-27 11:00 639234243654907465
545 ms 153.122.96.111
33 2026-08-27 10:43 639234233269654413
545 ms 153.122.96.111
32 2026-08-27 10:25 639234222943951923
552 ms 153.122.96.111
31 2026-08-27 10:08 639234212558002823
570 ms 153.122.96.111
30 2026-08-27 09:51 639234202117531850
529 ms 153.122.96.111
29 2026-08-27 09:33 639234191649612722
537 ms 153.122.96.111
28 2026-08-27 09:16 639234181105879568
544 ms 153.122.96.111
27 2026-08-27 08:58 639234170713214496
535 ms 153.122.96.111
26 2026-08-27 08:41 639234160341037652
554 ms 153.122.96.111
25 2026-08-27 08:24 639234149799404224
534 ms 153.122.96.111
24 2026-08-27 08:06 639234139553286469
559 ms 153.122.96.111
23 2026-08-27 07:13 639234107183588293
555 ms 153.122.96.111
22 2026-08-27 06:55 639234096905435724
533 ms 153.122.96.111
21 2026-08-27 06:38 639234086579410775
558 ms 153.122.96.111
20 2026-08-27 06:21 639234076291157956
548 ms 153.122.96.111
19 2026-08-27 06:04 639234065981939454
533 ms 153.122.96.111
18 2026-08-27 05:47 639234055548642997
544 ms 153.122.96.111
17 2026-08-27 05:29 639234045267979603
521 ms 153.122.96.111
16 2026-08-27 05:12 639234034999717463
567 ms 153.122.96.111
15 2026-08-27 04:55 639234024739225358
517 ms 153.122.96.111
14 2026-08-27 04:38 639234014311170162
547 ms 153.122.96.111
13 2026-08-27 04:20 639234003806017640
557 ms 153.122.96.111
12 2026-08-27 04:03 639233993356203030
555 ms 153.122.96.111
11 2026-08-27 03:09 639233961301716608
537 ms 153.122.96.111
10 2026-08-27 02:52 639233950834200647
584 ms 153.122.96.111
9 2026-08-27 02:35 639233940431849026
535 ms 153.122.96.111
8 2026-08-27 02:17 639233930110596398
540 ms 153.122.96.111
7 2026-08-27 02:00 639233919705434540
542 ms 153.122.96.111
6 2026-08-27 01:43 639233909452807845
556 ms 153.122.96.111
5 2026-08-27 01:26 639233899096420820
547 ms 153.122.96.111
4 2026-08-27 01:09 639233888707824939
523 ms 153.122.96.111
3 2026-08-27 00:51 639233878461203802
570 ms 153.122.96.111
2 2026-08-27 00:34 639233868060868209
542 ms 153.122.96.111
1 2026-08-27 00:17 639233857450922991
536 ms 153.122.96.111