DNS response history for ns3.datacenta.net

ns3.datacenta.net 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 30 DNS check records, 30 successful responses, 0 failed responses, and 330 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 ns3.datacenta.net.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

330 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 12:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

37.143.140.6

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns3.datacenta.net

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
30 2026-08-28 12:41 639235174453894956
133 ms 37.143.140.6
29 2026-08-28 12:24 639235163898672622
50 ms 37.143.140.6
28 2026-08-28 11:31 639235132147470568
2041 ms 37.143.140.6
27 2026-08-28 11:14 639235121907744088
54 ms 37.143.140.6
26 2026-08-28 10:56 639235111428014262
49 ms 37.143.140.6
25 2026-08-28 10:39 639235100921813626
53 ms 37.143.140.6
24 2026-08-28 09:45 639235068670703481
2037 ms 37.143.140.6
23 2026-08-28 09:28 639235058337459445
61 ms 37.143.140.6
22 2026-08-28 09:10 639235047825109146
17 ms 37.143.140.6
21 2026-08-28 08:53 639235037383229033
59 ms 37.143.140.6
20 2026-08-28 08:00 639235005619242711
66 ms 37.143.140.6
19 2026-08-28 07:43 639234995310346584
3 ms 37.143.140.6
18 2026-08-28 07:26 639234984946548933
98 ms 37.143.140.6
17 2026-08-28 07:08 639234974608077290
53 ms 37.143.140.6
16 2026-08-28 06:15 639234942529845595
93 ms 37.143.140.6
15 2026-08-28 05:58 639234932259126627
54 ms 37.143.140.6
14 2026-08-28 05:40 639234921916735988
54 ms 37.143.140.6
13 2026-08-28 05:23 639234911470038027
49 ms 37.143.140.6
12 2026-08-28 04:30 639234879588411654
30 ms 37.143.140.6
11 2026-08-28 04:13 639234869341589104
83 ms 37.143.140.6
10 2026-08-28 03:56 639234859012216675
25 ms 37.143.140.6
9 2026-08-28 03:38 639234848695364934
299 ms 37.143.140.6
8 2026-08-28 02:46 639234816952458162
2048 ms 37.143.140.6
7 2026-08-28 02:29 639234806773081598
45 ms 37.143.140.6
6 2026-08-28 02:11 639234796382955255
83 ms 37.143.140.6
5 2026-08-28 01:54 639234786015782563
45 ms 37.143.140.6
4 2026-08-28 01:00 639234753811917646
2049 ms 37.143.140.6
3 2026-08-28 00:44 639234743739767811
75 ms 37.143.140.6
2 2026-08-28 00:26 639234733372362811
28 ms 37.143.140.6
1 2026-08-28 00:09 639234723048550337
54 ms 37.143.140.6