DNS response history for ns2.datarafting.com

ns2.datarafting.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-28. For this date, NameServerHistory found 32 DNS check records, 31 successful responses, 1 failed responses, and 209 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.datarafting.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

209 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 13:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.159.10.142

Most recently resolved hosting IP on selected date

Successful Responses

31

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.datarafting.com

Showing DNS history for 2026-08-28 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
32 2026-08-28 13:19 639235195230848570
11 ms 162.159.10.142
31 2026-08-28 13:02 639235184840503274
10 ms 162.159.10.142
30 2026-08-28 12:44 639235174453894956
10 ms 162.159.10.142
29 2026-08-28 12:27 639235163898672622
18 ms 162.159.10.142
28 2026-08-28 11:34 639235132147470568
12 ms 162.159.10.142
27 2026-08-28 11:17 639235121907744088
-
26 2026-08-28 11:00 639235111428014262
10 ms 162.159.10.142
25 2026-08-28 10:42 639235100921813626
10 ms 162.159.10.142
24 2026-08-28 09:48 639235068670703481
12 ms 162.159.10.142
23 2026-08-28 09:31 639235058337459445
9 ms 162.159.10.142
22 2026-08-28 09:13 639235047825109146
23 ms 162.159.10.142
21 2026-08-28 08:56 639235037383229033
13 ms 162.159.10.142
20 2026-08-28 08:03 639235005619242711
11 ms 162.159.10.142
19 2026-08-28 07:46 639234995310346584
15 ms 162.159.10.142
18 2026-08-28 07:29 639234984946548933
17 ms 162.159.10.142
17 2026-08-28 07:11 639234974608077290
31 ms 162.159.10.142
16 2026-08-28 06:18 639234942529845595
25 ms 162.159.10.142
15 2026-08-28 06:01 639234932259126627
35 ms 162.159.10.142
14 2026-08-28 05:43 639234921916735988
11 ms 162.159.10.142
13 2026-08-28 05:26 639234911470038027
9 ms 162.159.10.142
12 2026-08-28 04:33 639234879588411654
16 ms 162.159.10.142
11 2026-08-28 04:16 639234869341589104
13 ms 162.159.10.142
10 2026-08-28 03:59 639234859012216675
12 ms 162.159.10.142
9 2026-08-28 03:41 639234848695364934
8 ms 162.159.10.142
8 2026-08-28 02:49 639234816952458162
27 ms 162.159.10.142
7 2026-08-28 02:32 639234806773081598
31 ms 162.159.10.142
6 2026-08-28 02:14 639234796382955255
2007 ms 162.159.10.142
5 2026-08-28 01:57 639234786015782563
6 ms 162.159.10.142
4 2026-08-28 01:03 639234753811917646
3 ms 162.159.10.142
3 2026-08-28 00:47 639234743739767811
26 ms 162.159.10.142
2 2026-08-28 00:29 639234733372362811
4023 ms 162.159.10.142
1 2026-08-28 00:12 639234723048550337
10 ms 162.159.10.142