DNS response history for ns2.meishivps.com

ns2.meishivps.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-27. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 460 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.meishivps.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

460 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

207.210.229.201

Most recently resolved hosting IP on selected date

Successful Responses

29

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

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
29 2026-08-27 09:30 639234191649612722
140 ms 207.210.229.201
28 2026-08-27 09:12 639234181105879568
313 ms 207.210.229.201
27 2026-08-27 08:55 639234170713214496
279 ms 207.210.229.201
26 2026-08-27 08:38 639234160341037652
312 ms 207.210.229.201
25 2026-08-27 08:20 639234149799404224
569 ms 207.210.229.201
24 2026-08-27 08:03 639234139553286469
315 ms 207.210.229.201
23 2026-08-27 07:09 639234107183588293
137 ms 207.210.229.201
22 2026-08-27 06:52 639234096905435724
289 ms 207.210.229.201
21 2026-08-27 06:35 639234086579410775
303 ms 207.210.229.201
20 2026-08-27 06:18 639234076291157956
2010 ms 207.210.229.201
19 2026-08-27 06:01 639234065981939454
280 ms 207.210.229.201
18 2026-08-27 05:43 639234055548642997
138 ms 207.210.229.201
17 2026-08-27 05:26 639234045267979603
283 ms 207.210.229.201
16 2026-08-27 05:09 639234034999717463
283 ms 207.210.229.201
15 2026-08-27 04:52 639234024739225358
151 ms 207.210.229.201
14 2026-08-27 04:34 639234014311170162
270 ms 207.210.229.201
13 2026-08-27 04:17 639234003806017640
140 ms 207.210.229.201
12 2026-08-27 03:59 639233993356203030
281 ms 207.210.229.201
11 2026-08-27 03:06 639233961301716608
293 ms 207.210.229.201
10 2026-08-27 02:49 639233950834200647
2139 ms 207.210.229.201
9 2026-08-27 02:31 639233940431849026
289 ms 207.210.229.201
8 2026-08-27 02:14 639233930110596398
280 ms 207.210.229.201
7 2026-08-27 01:57 639233919705434540
272 ms 207.210.229.201
6 2026-08-27 01:40 639233909452807845
288 ms 207.210.229.201
5 2026-08-27 01:22 639233899096420820
271 ms 207.210.229.201
4 2026-08-27 01:05 639233888707824939
272 ms 207.210.229.201
3 2026-08-27 00:48 639233878461203802
280 ms 207.210.229.201
2 2026-08-27 00:31 639233868060868209
300 ms 207.210.229.201
1 2026-08-27 00:13 639233857450922991
2149 ms 207.210.229.201