DNS response history for dragon.bjut.edu.cn

dragon.bjut.edu.cn 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 30 DNS check records, 30 successful responses, 0 failed responses, and 591 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 dragon.bjut.edu.cn.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

591 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.112.78.1

Most recently resolved hosting IP on selected date

Successful Responses

30

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 dragon.bjut.edu.cn

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
30 2026-08-25 10:21 639232492740373468
285 ms 202.112.78.1
29 2026-08-25 10:04 639232482235303141
833 ms 202.112.78.1
28 2026-08-25 09:46 639232471861770303
790 ms 202.112.78.1
27 2026-08-25 09:29 639232461630217327
257 ms 202.112.78.1
26 2026-08-25 09:12 639232451282965990
287 ms 202.112.78.1
25 2026-08-25 08:55 639232440814614938
712 ms 202.112.78.1
24 2026-08-25 08:37 639232430410720425
232 ms 202.112.78.1
23 2026-08-25 08:20 639232420003096185
528 ms 202.112.78.1
22 2026-08-25 08:02 639232409467287444
254 ms 202.112.78.1
21 2026-08-25 07:45 639232399077195997
272 ms 202.112.78.1
20 2026-08-25 07:28 639232388731528337
263 ms 202.112.78.1
19 2026-08-25 07:10 639232378288598612
841 ms 202.112.78.1
18 2026-08-25 06:16 639232346196373643
614 ms 202.112.78.1
17 2026-08-25 06:00 639232336112370741
555 ms 202.112.78.1
16 2026-08-25 05:43 639232326146508970
2661 ms 202.112.78.1
15 2026-08-25 05:26 639232316189381720
740 ms 202.112.78.1
14 2026-08-25 05:10 639232306217998913
540 ms 202.112.78.1
13 2026-08-25 04:53 639232296255744174
542 ms 202.112.78.1
12 2026-08-25 04:36 639232286095760789
554 ms 202.112.78.1
11 2026-08-25 04:19 639232276086186273
260 ms 202.112.78.1
10 2026-08-25 04:03 639232265900986425
727 ms 202.112.78.1
9 2026-08-25 03:46 639232255723518075
785 ms 202.112.78.1
8 2026-08-25 03:29 639232245484452890
543 ms 202.112.78.1
7 2026-08-25 03:12 639232235157175331
260 ms 202.112.78.1
6 2026-08-25 02:18 639232203197189095
816 ms 202.112.78.1
5 2026-08-25 02:01 639232192844564298
261 ms 202.112.78.1
4 2026-08-25 01:44 639232182496008942
487 ms 202.112.78.1
3 2026-08-25 01:27 639232172197053132
796 ms 202.112.78.1
2 2026-08-25 00:33 639232140250307418
261 ms 202.112.78.1
1 2026-08-25 00:16 639232129927860324
766 ms 202.112.78.1