DNS response history for ns2.syncmark.com

ns2.syncmark.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 385 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.syncmark.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

385 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

153.122.84.94

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.syncmark.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
552 ms 153.122.84.94
32 2026-08-26 10:09 639233350067824371
559 ms 153.122.84.94
31 2026-08-26 09:52 639233339545274518
543 ms 153.122.84.94
30 2026-08-26 09:34 639233329214918079
4 ms 153.122.84.94
29 2026-08-26 09:17 639233318749762337
553 ms 153.122.84.94
28 2026-08-26 09:00 639233308387917838
556 ms 153.122.84.94
27 2026-08-26 08:43 639233297961740122
551 ms 153.122.84.94
26 2026-08-26 08:25 639233287487159094
553 ms 153.122.84.94
25 2026-08-26 08:08 639233276995531707
7 ms 153.122.84.94
24 2026-08-26 07:50 639233266521568229
558 ms 153.122.84.94
23 2026-08-26 07:33 639233256081047431
552 ms 153.122.84.94
22 2026-08-26 06:39 639233223620132921
564 ms 153.122.84.94
21 2026-08-26 06:21 639233213287814244
9 ms 153.122.84.94
20 2026-08-26 06:04 639233202925983161
295 ms 153.122.84.94
19 2026-08-26 05:47 639233192644780696
9 ms 153.122.84.94
18 2026-08-26 05:30 639233182401183833
549 ms 153.122.84.94
17 2026-08-26 05:13 639233172074181051
4 ms 153.122.84.94
16 2026-08-26 04:55 639233161808421455
2 ms 153.122.84.94
15 2026-08-26 04:38 639233151357344052
561 ms 153.122.84.94
14 2026-08-26 04:21 639233141034116946
548 ms 153.122.84.94
13 2026-08-26 04:04 639233130828334142
554 ms 153.122.84.94
12 2026-08-26 03:47 639233120373450007
560 ms 153.122.84.94
11 2026-08-26 03:29 639233110066216193
559 ms 153.122.84.94
10 2026-08-26 02:36 639233078065410564
535 ms 153.122.84.94
9 2026-08-26 02:19 639233067787457832
3 ms 153.122.84.94
8 2026-08-26 02:02 639233057501801162
552 ms 153.122.84.94
7 2026-08-26 01:45 639233047089431703
519 ms 153.122.84.94
6 2026-08-26 01:27 639233036754790688
527 ms 153.122.84.94
5 2026-08-26 01:10 639233026412602472
282 ms 153.122.84.94
4 2026-08-26 00:53 639233016064066127
532 ms 153.122.84.94
3 2026-08-26 00:36 639233005922655772
4 ms 153.122.84.94
2 2026-08-26 00:19 639232995672256907
9 ms 153.122.84.94
1 2026-08-26 00:01 639232985300872416
534 ms 153.122.84.94