DNS response history for ns1.nosayapi.com

ns1.nosayapi.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-30. For this date, NameServerHistory found 36 DNS check records, 35 successful responses, 1 failed responses, and 234 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 ns1.nosayapi.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

234 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 11:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

37.230.110.110

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns1.nosayapi.com

Showing DNS history for 2026-08-30 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-30 11:49 639236867916029489
1552 ms 37.230.110.110
35 2026-08-30 11:32 639236858088772005
110 ms 37.230.110.110
34 2026-08-30 11:16 639236848158742395
7 ms 37.230.110.110
33 2026-08-30 10:59 639236838137395574
113 ms 37.230.110.110
32 2026-08-30 10:42 639236827967386881
117 ms 37.230.110.110
31 2026-08-30 10:25 639236817708615077
112 ms 37.230.110.110
30 2026-08-30 09:32 639236785770651804
149 ms 37.230.110.110
29 2026-08-30 09:15 639236775820686373
-
28 2026-08-30 08:58 639236765768339082
108 ms 37.230.110.110
27 2026-08-30 08:42 639236755602384085
2033 ms 37.230.110.110
26 2026-08-30 08:25 639236745600094925
110 ms 37.230.110.110
25 2026-08-30 08:08 639236735311262753
112 ms 37.230.110.110
24 2026-08-30 07:51 639236724996745235
87 ms 37.230.110.110
23 2026-08-30 07:34 639236714839899761
153 ms 37.230.110.110
22 2026-08-30 07:17 639236704748431488
3 ms 37.230.110.110
21 2026-08-30 07:00 639236694430128550
79 ms 37.230.110.110
20 2026-08-30 06:43 639236684143292417
111 ms 37.230.110.110
19 2026-08-30 06:26 639236673972499943
55 ms 37.230.110.110
18 2026-08-30 05:32 639236642126522802
3 ms 37.230.110.110
17 2026-08-30 05:16 639236632183518198
25 ms 37.230.110.110
16 2026-08-30 04:59 639236622289312589
3 ms 37.230.110.110
15 2026-08-30 04:43 639236612490676525
131 ms 37.230.110.110
14 2026-08-30 04:26 639236602582494852
13 ms 37.230.110.110
13 2026-08-30 04:10 639236592511706469
108 ms 37.230.110.110
12 2026-08-30 03:53 639236582441006869
8 ms 37.230.110.110
11 2026-08-30 03:36 639236572478785089
110 ms 37.230.110.110
10 2026-08-30 03:20 639236562556749999
111 ms 37.230.110.110
9 2026-08-30 03:03 639236552353482281
115 ms 37.230.110.110
8 2026-08-30 02:46 639236542188881607
2044 ms 37.230.110.110
7 2026-08-30 02:29 639236531885440105
98 ms 37.230.110.110
6 2026-08-30 01:35 639236499922985383
109 ms 37.230.110.110
5 2026-08-30 01:19 639236489713594431
68 ms 37.230.110.110
4 2026-08-30 01:02 639236479750443901
109 ms 37.230.110.110
3 2026-08-30 00:45 639236469719936375
3 ms 37.230.110.110
2 2026-08-30 00:28 639236459579244885
122 ms 37.230.110.110
1 2026-08-30 00:12 639236449582837549
4 ms 37.230.110.110