DNS response history for ns1.betsync.app

ns1.betsync.app 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 34 DNS check records, 34 successful responses, 0 failed responses, and 108 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 ns1.betsync.app.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

108 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

178.156.138.33

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns1.betsync.app

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
34 2026-08-26 11:30 639233403515141099
27 ms 178.156.138.33
33 2026-08-26 10:35 639233370841350248
103 ms 178.156.138.33
32 2026-08-26 10:18 639233360361507238
6 ms 178.156.138.33
31 2026-08-26 10:00 639233350067824371
212 ms 178.156.138.33
30 2026-08-26 09:43 639233339545274518
42 ms 178.156.138.33
29 2026-08-26 09:26 639233329214918079
50 ms 178.156.138.33
28 2026-08-26 09:08 639233318749762337
34 ms 178.156.138.33
27 2026-08-26 08:51 639233308387917838
13 ms 178.156.138.33
26 2026-08-26 08:34 639233297961740122
11 ms 178.156.138.33
25 2026-08-26 08:16 639233287487159094
53 ms 178.156.138.33
24 2026-08-26 07:59 639233276995531707
194 ms 178.156.138.33
23 2026-08-26 07:41 639233266521568229
13 ms 178.156.138.33
22 2026-08-26 07:24 639233256081047431
15 ms 178.156.138.33
21 2026-08-26 06:30 639233223620132921
38 ms 178.156.138.33
20 2026-08-26 06:13 639233213287814244
43 ms 178.156.138.33
19 2026-08-26 05:55 639233202925983161
12 ms 178.156.138.33
18 2026-08-26 05:38 639233192644780696
21 ms 178.156.138.33
17 2026-08-26 05:21 639233182401183833
52 ms 178.156.138.33
16 2026-08-26 05:04 639233172074181051
34 ms 178.156.138.33
15 2026-08-26 04:47 639233161808421455
150 ms 178.156.138.33
14 2026-08-26 04:29 639233151357344052
22 ms 178.156.138.33
13 2026-08-26 04:12 639233141034116946
11 ms 178.156.138.33
12 2026-08-26 03:55 639233130828334142
72 ms 178.156.138.33
11 2026-08-26 03:38 639233120373450007
2036 ms 178.156.138.33
10 2026-08-26 03:20 639233110066216193
52 ms 178.156.138.33
9 2026-08-26 02:27 639233078065410564
31 ms 178.156.138.33
8 2026-08-26 02:10 639233067787457832
27 ms 178.156.138.33
7 2026-08-26 01:53 639233057501801162
38 ms 178.156.138.33
6 2026-08-26 01:36 639233047089431703
20 ms 178.156.138.33
5 2026-08-26 01:18 639233036754790688
18 ms 178.156.138.33
4 2026-08-26 01:01 639233026412602472
11 ms 178.156.138.33
3 2026-08-26 00:44 639233016064066127
74 ms 178.156.138.33
2 2026-08-26 00:27 639233005922655772
103 ms 178.156.138.33
1 2026-08-26 00:10 639232995672256907
22 ms 178.156.138.33