DNS response history for ns2.bridge-kyoto.com

ns2.bridge-kyoto.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 35 DNS check records, 35 successful responses, 0 failed responses, and 390 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.bridge-kyoto.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

390 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.167.17.179

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 ns2.bridge-kyoto.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
35 2026-08-25 12:24 639232566381512620
289 ms 210.167.17.179
34 2026-08-25 12:07 639232556111768563
557 ms 210.167.17.179
33 2026-08-25 11:50 639232545839529039
547 ms 210.167.17.179
32 2026-08-25 11:32 639232535349285207
317 ms 210.167.17.179
31 2026-08-25 11:15 639232524938080723
538 ms 210.167.17.179
30 2026-08-25 10:21 639232492740373468
545 ms 210.167.17.179
29 2026-08-25 10:04 639232482235303141
524 ms 210.167.17.179
28 2026-08-25 09:46 639232471861770303
4 ms 210.167.17.179
27 2026-08-25 09:29 639232461630217327
3 ms 210.167.17.179
26 2026-08-25 09:12 639232451282965990
538 ms 210.167.17.179
25 2026-08-25 08:55 639232440814614938
4 ms 210.167.17.179
24 2026-08-25 08:37 639232430410720425
556 ms 210.167.17.179
23 2026-08-25 08:20 639232420003096185
4 ms 210.167.17.179
22 2026-08-25 08:03 639232409467287444
566 ms 210.167.17.179
21 2026-08-25 07:45 639232399077195997
563 ms 210.167.17.179
20 2026-08-25 07:28 639232388731528337
535 ms 210.167.17.179
19 2026-08-25 07:10 639232378288598612
570 ms 210.167.17.179
18 2026-08-25 06:17 639232346196373643
536 ms 210.167.17.179
17 2026-08-25 06:00 639232336112370741
348 ms 210.167.17.179
16 2026-08-25 05:43 639232326146508970
524 ms 210.167.17.179
15 2026-08-25 05:27 639232316189381720
552 ms 210.167.17.179
14 2026-08-25 05:10 639232306217998913
288 ms 210.167.17.179
13 2026-08-25 04:53 639232296255744174
383 ms 210.167.17.179
12 2026-08-25 04:37 639232286095760789
4 ms 210.167.17.179
11 2026-08-25 04:20 639232276086186273
529 ms 210.167.17.179
10 2026-08-25 04:03 639232265900986425
2 ms 210.167.17.179
9 2026-08-25 03:46 639232255723518075
542 ms 210.167.17.179
8 2026-08-25 03:29 639232245484452890
533 ms 210.167.17.179
7 2026-08-25 03:12 639232235157175331
344 ms 210.167.17.179
6 2026-08-25 02:18 639232203197189095
543 ms 210.167.17.179
5 2026-08-25 02:01 639232192844564298
318 ms 210.167.17.179
4 2026-08-25 01:44 639232182496008942
341 ms 210.167.17.179
3 2026-08-25 01:27 639232172197053132
275 ms 210.167.17.179
2 2026-08-25 00:33 639232140250307418
551 ms 210.167.17.179
1 2026-08-25 00:17 639232129927860324
371 ms 210.167.17.179