DNS response history for ns2.milvusapp.com

ns2.milvusapp.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-24. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 434 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.milvusapp.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

434 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

125.131.213.7

Most recently resolved hosting IP on selected date

Successful Responses

33

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.milvusapp.com

Showing DNS history for 2026-08-24 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
33 2026-08-24 13:54 639231755868832964
412 ms 125.131.213.7
32 2026-08-24 13:37 639231745628278877
413 ms 125.131.213.7
31 2026-08-24 13:20 639231735407682062
417 ms 125.131.213.7
30 2026-08-24 12:27 639231703815441688
493 ms 125.131.213.7
29 2026-08-24 12:10 639231693747052549
459 ms 125.131.213.7
28 2026-08-24 11:53 639231683712487276
496 ms 125.131.213.7
27 2026-08-24 11:37 639231673513573868
417 ms 125.131.213.7
26 2026-08-24 10:43 639231641791249939
431 ms 125.131.213.7
25 2026-08-24 10:27 639231631866211033
488 ms 125.131.213.7
24 2026-08-24 10:10 639231621644955316
412 ms 125.131.213.7
23 2026-08-24 09:53 639231611478799259
417 ms 125.131.213.7
22 2026-08-24 09:00 639231579923718211
421 ms 125.131.213.7
21 2026-08-24 08:44 639231569810702936
414 ms 125.131.213.7
20 2026-08-24 08:27 639231559762411619
460 ms 125.131.213.7
19 2026-08-24 08:10 639231549663595407
420 ms 125.131.213.7
18 2026-08-24 07:17 639231518076817246
470 ms 125.131.213.7
17 2026-08-24 07:01 639231508078650885
410 ms 125.131.213.7
16 2026-08-24 06:44 639231498210697093
410 ms 125.131.213.7
15 2026-08-24 06:27 639231488109699360
474 ms 125.131.213.7
14 2026-08-24 05:35 639231456772510692
427 ms 125.131.213.7
13 2026-08-24 05:19 639231447084631185
451 ms 125.131.213.7
12 2026-08-24 05:02 639231437208519473
452 ms 125.131.213.7
11 2026-08-24 04:46 639231427209627490
434 ms 125.131.213.7
10 2026-08-24 03:53 639231395791246644
368 ms 125.131.213.7
9 2026-08-24 03:37 639231386075551458
410 ms 125.131.213.7
8 2026-08-24 03:21 639231376208713791
454 ms 125.131.213.7
7 2026-08-24 03:04 639231366170589276
457 ms 125.131.213.7
6 2026-08-24 02:12 639231334732159368
420 ms 125.131.213.7
5 2026-08-24 01:55 639231325035670078
411 ms 125.131.213.7
4 2026-08-24 01:39 639231315132253837
412 ms 125.131.213.7
3 2026-08-24 01:22 639231305014280808
417 ms 125.131.213.7
2 2026-08-24 00:30 639231273779380675
409 ms 125.131.213.7
1 2026-08-24 00:14 639231264180839154
453 ms 125.131.213.7