DNS response history for ns.jscom.net

ns.jscom.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-27. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 493 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 ns.jscom.net.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

493 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

219.166.102.115

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns.jscom.net

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
37 2026-08-27 12:27 639234296664302575
475 ms 219.166.102.115
36 2026-08-27 12:10 639234286253196126
651 ms 219.166.102.115
35 2026-08-27 11:16 639234253963286387
2009 ms 219.166.102.115
34 2026-08-27 10:59 639234243654907465
479 ms 219.166.102.115
33 2026-08-27 10:41 639234233269654413
277 ms 219.166.102.115
32 2026-08-27 10:24 639234222943951923
508 ms 219.166.102.115
31 2026-08-27 10:07 639234212558002823
698 ms 219.166.102.115
30 2026-08-27 09:50 639234202117531850
524 ms 219.166.102.115
29 2026-08-27 09:32 639234191649612722
464 ms 219.166.102.115
28 2026-08-27 09:15 639234181105879568
491 ms 219.166.102.115
27 2026-08-27 08:57 639234170713214496
559 ms 219.166.102.115
26 2026-08-27 08:40 639234160341037652
504 ms 219.166.102.115
25 2026-08-27 08:22 639234149799404224
536 ms 219.166.102.115
24 2026-08-27 08:05 639234139553286469
491 ms 219.166.102.115
23 2026-08-27 07:11 639234107183588293
477 ms 219.166.102.115
22 2026-08-27 06:54 639234096905435724
10 ms 219.166.102.115
21 2026-08-27 06:37 639234086579410775
460 ms 219.166.102.115
20 2026-08-27 06:20 639234076291157956
480 ms 219.166.102.115
19 2026-08-27 06:03 639234065981939454
7 ms 219.166.102.115
18 2026-08-27 05:45 639234055548642997
466 ms 219.166.102.115
17 2026-08-27 05:28 639234045267979603
476 ms 219.166.102.115
16 2026-08-27 05:11 639234034999717463
521 ms 219.166.102.115
15 2026-08-27 04:54 639234024739225358
281 ms 219.166.102.115
14 2026-08-27 04:37 639234014311170162
741 ms 219.166.102.115
13 2026-08-27 04:19 639234003806017640
496 ms 219.166.102.115
12 2026-08-27 04:02 639233993356203030
714 ms 219.166.102.115
11 2026-08-27 03:08 639233961301716608
534 ms 219.166.102.115
10 2026-08-27 02:51 639233950834200647
302 ms 219.166.102.115
9 2026-08-27 02:33 639233940431849026
248 ms 219.166.102.115
8 2026-08-27 02:16 639233930110596398
499 ms 219.166.102.115
7 2026-08-27 01:59 639233919705434540
493 ms 219.166.102.115
6 2026-08-27 01:42 639233909452807845
463 ms 219.166.102.115
5 2026-08-27 01:24 639233899096420820
468 ms 219.166.102.115
4 2026-08-27 01:07 639233888707824939
475 ms 219.166.102.115
3 2026-08-27 00:50 639233878461203802
474 ms 219.166.102.115
2 2026-08-27 00:33 639233868060868209
474 ms 219.166.102.115
1 2026-08-27 00:15 639233857450922991
7 ms 219.166.102.115