DNS response history for ns1.saidms.com

ns1.saidms.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-25. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 400 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.saidms.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

400 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.214.99.204

Most recently resolved hosting IP on selected date

Successful Responses

35

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

Showing DNS history for 2026-08-25 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
35 2026-08-25 12:21 639232566381512620
331 ms 162.214.99.204
34 2026-08-25 12:04 639232556111768563
2155 ms 162.214.99.204
33 2026-08-25 11:47 639232545839529039
168 ms 162.214.99.204
32 2026-08-25 11:30 639232535349285207
166 ms 162.214.99.204
31 2026-08-25 11:12 639232524938080723
328 ms 162.214.99.204
30 2026-08-25 10:19 639232492740373468
322 ms 162.214.99.204
29 2026-08-25 10:01 639232482235303141
322 ms 162.214.99.204
28 2026-08-25 09:44 639232471861770303
11 ms 162.214.99.204
27 2026-08-25 09:27 639232461630217327
206 ms 162.214.99.204
26 2026-08-25 09:10 639232451282965990
328 ms 162.214.99.204
25 2026-08-25 08:52 639232440814614938
2181 ms 162.214.99.204
24 2026-08-25 08:35 639232430410720425
170 ms 162.214.99.204
23 2026-08-25 08:18 639232420003096185
325 ms 162.214.99.204
22 2026-08-25 08:00 639232409467287444
2163 ms 162.214.99.204
21 2026-08-25 07:43 639232399077195997
315 ms 162.214.99.204
20 2026-08-25 07:25 639232388731528337
326 ms 162.214.99.204
19 2026-08-25 07:08 639232378288598612
323 ms 162.214.99.204
18 2026-08-25 06:14 639232346196373643
5 ms 162.214.99.204
17 2026-08-25 05:57 639232336112370741
161 ms 162.214.99.204
16 2026-08-25 05:41 639232326146508970
318 ms 162.214.99.204
15 2026-08-25 05:24 639232316189381720
4 ms 162.214.99.204
14 2026-08-25 05:08 639232306217998913
4 ms 162.214.99.204
13 2026-08-25 04:51 639232296255744174
4 ms 162.214.99.204
12 2026-08-25 04:34 639232286095760789
161 ms 162.214.99.204
11 2026-08-25 04:17 639232276086186273
319 ms 162.214.99.204
10 2026-08-25 04:01 639232265900986425
322 ms 162.214.99.204
9 2026-08-25 03:44 639232255723518075
319 ms 162.214.99.204
8 2026-08-25 03:27 639232245484452890
173 ms 162.214.99.204
7 2026-08-25 03:09 639232235157175331
321 ms 162.214.99.204
6 2026-08-25 02:16 639232203197189095
319 ms 162.214.99.204
5 2026-08-25 01:59 639232192844564298
315 ms 162.214.99.204
4 2026-08-25 01:42 639232182496008942
161 ms 162.214.99.204
3 2026-08-25 01:24 639232172197053132
326 ms 162.214.99.204
2 2026-08-25 00:31 639232140250307418
323 ms 162.214.99.204
1 2026-08-25 00:14 639232129927860324
319 ms 162.214.99.204