DNS response history for ns2.4js.com

ns2.4js.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-27. For this date, NameServerHistory found 39 DNS check records, 39 successful responses, 0 failed responses, and 122 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.4js.com.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

122 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

158.69.113.141

Most recently resolved hosting IP on selected date

Successful Responses

39

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.4js.com

Showing DNS history for 2026-08-27 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
39 2026-08-27 12:52 639234317475724313
89 ms 158.69.113.141
38 2026-08-27 12:35 639234307007468133
138 ms 158.69.113.141
37 2026-08-27 12:18 639234296664302575
476 ms 158.69.113.141
36 2026-08-27 12:00 639234286253196126
58 ms 158.69.113.141
35 2026-08-27 11:07 639234253963286387
36 ms 158.69.113.141
34 2026-08-27 10:49 639234243654907465
23 ms 158.69.113.141
33 2026-08-27 10:32 639234233269654413
42 ms 158.69.113.141
32 2026-08-27 10:15 639234222943951923
137 ms 158.69.113.141
31 2026-08-27 09:58 639234212558002823
91 ms 158.69.113.141
30 2026-08-27 09:40 639234202117531850
170 ms 158.69.113.141
29 2026-08-27 09:23 639234191649612722
202 ms 158.69.113.141
28 2026-08-27 09:05 639234181105879568
120 ms 158.69.113.141
27 2026-08-27 08:48 639234170713214496
102 ms 158.69.113.141
26 2026-08-27 08:30 639234160341037652
28 ms 158.69.113.141
25 2026-08-27 08:13 639234149799404224
136 ms 158.69.113.141
24 2026-08-27 07:56 639234139553286469
35 ms 158.69.113.141
23 2026-08-27 07:02 639234107183588293
34 ms 158.69.113.141
22 2026-08-27 06:45 639234096905435724
187 ms 158.69.113.141
21 2026-08-27 06:28 639234086579410775
219 ms 158.69.113.141
20 2026-08-27 06:10 639234076291157956
214 ms 158.69.113.141
19 2026-08-27 05:53 639234065981939454
260 ms 158.69.113.141
18 2026-08-27 05:36 639234055548642997
125 ms 158.69.113.141
17 2026-08-27 05:19 639234045267979603
96 ms 158.69.113.141
16 2026-08-27 05:02 639234034999717463
241 ms 158.69.113.141
15 2026-08-27 04:45 639234024739225358
229 ms 158.69.113.141
14 2026-08-27 04:27 639234014311170162
137 ms 158.69.113.141
13 2026-08-27 04:10 639234003806017640
132 ms 158.69.113.141
12 2026-08-27 03:52 639233993356203030
79 ms 158.69.113.141
11 2026-08-27 02:59 639233961301716608
145 ms 158.69.113.141
10 2026-08-27 02:42 639233950834200647
37 ms 158.69.113.141
9 2026-08-27 02:24 639233940431849026
35 ms 158.69.113.141
8 2026-08-27 02:07 639233930110596398
102 ms 158.69.113.141
7 2026-08-27 01:49 639233919705434540
135 ms 158.69.113.141
6 2026-08-27 01:32 639233909452807845
103 ms 158.69.113.141
5 2026-08-27 01:15 639233899096420820
58 ms 158.69.113.141
4 2026-08-27 00:58 639233888707824939
37 ms 158.69.113.141
3 2026-08-27 00:41 639233878461203802
39 ms 158.69.113.141
2 2026-08-27 00:23 639233868060868209
149 ms 158.69.113.141
1 2026-08-27 00:06 639233857450922991
85 ms 158.69.113.141