DNS response history for ns2.sweet-dating-online.com

ns2.sweet-dating-online.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 36 DNS check records, 36 successful responses, 0 failed responses, and 165 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.sweet-dating-online.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

165 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.38.166.203

Most recently resolved hosting IP on selected date

Successful Responses

36

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.sweet-dating-online.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
36 2026-08-26 12:03 639233424567558554
43 ms 212.38.166.203
35 2026-08-26 11:46 639233414056832719
44 ms 212.38.166.203
34 2026-08-26 11:28 639233403515141099
52 ms 212.38.166.203
33 2026-08-26 10:33 639233370841350248
136 ms 212.38.166.203
32 2026-08-26 10:16 639233360361507238
50 ms 212.38.166.203
31 2026-08-26 09:59 639233350067824371
42 ms 212.38.166.203
30 2026-08-26 09:41 639233339545274518
60 ms 212.38.166.203
29 2026-08-26 09:24 639233329214918079
57 ms 212.38.166.203
28 2026-08-26 09:07 639233318749762337
84 ms 212.38.166.203
27 2026-08-26 08:49 639233308387917838
23 ms 212.38.166.203
26 2026-08-26 08:32 639233297961740122
30 ms 212.38.166.203
25 2026-08-26 08:15 639233287487159094
65 ms 212.38.166.203
24 2026-08-26 07:57 639233276995531707
55 ms 212.38.166.203
23 2026-08-26 07:40 639233266521568229
53 ms 212.38.166.203
22 2026-08-26 07:22 639233256081047431
49 ms 212.38.166.203
21 2026-08-26 06:28 639233223620132921
63 ms 212.38.166.203
20 2026-08-26 06:11 639233213287814244
38 ms 212.38.166.203
19 2026-08-26 05:54 639233202925983161
67 ms 212.38.166.203
18 2026-08-26 05:36 639233192644780696
83 ms 212.38.166.203
17 2026-08-26 05:19 639233182401183833
64 ms 212.38.166.203
16 2026-08-26 05:02 639233172074181051
2039 ms 212.38.166.203
15 2026-08-26 04:45 639233161808421455
41 ms 212.38.166.203
14 2026-08-26 04:28 639233151357344052
57 ms 212.38.166.203
13 2026-08-26 04:10 639233141034116946
52 ms 212.38.166.203
12 2026-08-26 03:53 639233130828334142
41 ms 212.38.166.203
11 2026-08-26 03:36 639233120373450007
41 ms 212.38.166.203
10 2026-08-26 03:19 639233110066216193
42 ms 212.38.166.203
9 2026-08-26 02:25 639233078065410564
91 ms 212.38.166.203
8 2026-08-26 02:08 639233067787457832
43 ms 212.38.166.203
7 2026-08-26 01:51 639233057501801162
26 ms 212.38.166.203
6 2026-08-26 01:34 639233047089431703
26 ms 212.38.166.203
5 2026-08-26 01:17 639233036754790688
84 ms 212.38.166.203
4 2026-08-26 00:59 639233026412602472
56 ms 212.38.166.203
3 2026-08-26 00:42 639233016064066127
40 ms 212.38.166.203
2 2026-08-26 00:25 639233005922655772
2053 ms 212.38.166.203
1 2026-08-26 00:08 639232995672256907
42 ms 212.38.166.203