DNS response history for ns3.inspur.com

ns3.inspur.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 28 DNS check records, 28 successful responses, 0 failed responses, and 393 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 ns3.inspur.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

393 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

58.56.83.250

Most recently resolved hosting IP on selected date

Successful Responses

28

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 ns3.inspur.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
28 2026-08-25 09:46 639232471861770303
591 ms 58.56.83.250
27 2026-08-25 09:29 639232461630217327
537 ms 58.56.83.250
26 2026-08-25 09:12 639232451282965990
327 ms 58.56.83.250
25 2026-08-25 08:54 639232440814614938
291 ms 58.56.83.250
24 2026-08-25 08:37 639232430410720425
241 ms 58.56.83.250
23 2026-08-25 08:20 639232420003096185
239 ms 58.56.83.250
22 2026-08-25 08:02 639232409467287444
551 ms 58.56.83.250
21 2026-08-25 07:45 639232399077195997
537 ms 58.56.83.250
20 2026-08-25 07:27 639232388731528337
277 ms 58.56.83.250
19 2026-08-25 07:10 639232378288598612
605 ms 58.56.83.250
18 2026-08-25 06:16 639232346196373643
268 ms 58.56.83.250
17 2026-08-25 06:00 639232336112370741
547 ms 58.56.83.250
16 2026-08-25 05:43 639232326146508970
12 ms 58.56.83.250
15 2026-08-25 05:26 639232316189381720
3 ms 58.56.83.250
14 2026-08-25 05:10 639232306217998913
3 ms 58.56.83.250
13 2026-08-25 04:53 639232296255744174
296 ms 58.56.83.250
12 2026-08-25 04:36 639232286095760789
299 ms 58.56.83.250
11 2026-08-25 04:19 639232276086186273
538 ms 58.56.83.250
10 2026-08-25 04:03 639232265900986425
587 ms 58.56.83.250
9 2026-08-25 03:46 639232255723518075
525 ms 58.56.83.250
8 2026-08-25 03:29 639232245484452890
298 ms 58.56.83.250
7 2026-08-25 03:12 639232235157175331
579 ms 58.56.83.250
6 2026-08-25 02:18 639232203197189095
580 ms 58.56.83.250
5 2026-08-25 02:01 639232192844564298
307 ms 58.56.83.250
4 2026-08-25 01:44 639232182496008942
547 ms 58.56.83.250
3 2026-08-25 01:27 639232172197053132
261 ms 58.56.83.250
2 2026-08-25 00:33 639232140250307418
574 ms 58.56.83.250
1 2026-08-25 00:16 639232129927860324
579 ms 58.56.83.250