DNS response history for ns2.ap-car.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

450 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:27

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

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.ap-car.com

Showing DNS history for 2026-08-26 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-26 10:27 639233360361507238
292 ms 210.167.17.179
32 2026-08-26 10:10 639233350067824371
264 ms 210.167.17.179
31 2026-08-26 09:53 639233339545274518
564 ms 210.167.17.179
30 2026-08-26 09:35 639233329214918079
531 ms 210.167.17.179
29 2026-08-26 09:18 639233318749762337
15 ms 210.167.17.179
28 2026-08-26 09:01 639233308387917838
553 ms 210.167.17.179
27 2026-08-26 08:43 639233297961740122
333 ms 210.167.17.179
26 2026-08-26 08:26 639233287487159094
299 ms 210.167.17.179
25 2026-08-26 08:09 639233276995531707
356 ms 210.167.17.179
24 2026-08-26 07:51 639233266521568229
658 ms 210.167.17.179
23 2026-08-26 07:33 639233256081047431
574 ms 210.167.17.179
22 2026-08-26 06:39 639233223620132921
556 ms 210.167.17.179
21 2026-08-26 06:22 639233213287814244
556 ms 210.167.17.179
20 2026-08-26 06:05 639233202925983161
563 ms 210.167.17.179
19 2026-08-26 05:48 639233192644780696
571 ms 210.167.17.179
18 2026-08-26 05:30 639233182401183833
358 ms 210.167.17.179
17 2026-08-26 05:14 639233172074181051
562 ms 210.167.17.179
16 2026-08-26 04:56 639233161808421455
565 ms 210.167.17.179
15 2026-08-26 04:39 639233151357344052
354 ms 210.167.17.179
14 2026-08-26 04:22 639233141034116946
559 ms 210.167.17.179
13 2026-08-26 04:05 639233130828334142
579 ms 210.167.17.179
12 2026-08-26 03:47 639233120373450007
340 ms 210.167.17.179
11 2026-08-26 03:30 639233110066216193
312 ms 210.167.17.179
10 2026-08-26 02:37 639233078065410564
324 ms 210.167.17.179
9 2026-08-26 02:20 639233067787457832
526 ms 210.167.17.179
8 2026-08-26 02:02 639233057501801162
561 ms 210.167.17.179
7 2026-08-26 01:45 639233047089431703
288 ms 210.167.17.179
6 2026-08-26 01:28 639233036754790688
547 ms 210.167.17.179
5 2026-08-26 01:11 639233026412602472
299 ms 210.167.17.179
4 2026-08-26 00:53 639233016064066127
538 ms 210.167.17.179
3 2026-08-26 00:36 639233005922655772
339 ms 210.167.17.179
2 2026-08-26 00:19 639232995672256907
555 ms 210.167.17.179
1 2026-08-26 00:02 639232985300872416
564 ms 210.167.17.179