DNS response history for ns1.samabebali.com

ns1.samabebali.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 228 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.samabebali.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

228 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.214.181.110

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.samabebali.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:24 639232566381512620
479 ms 95.214.181.110
34 2026-08-25 12:06 639232556111768563
194 ms 95.214.181.110
33 2026-08-25 11:49 639232545839529039
250 ms 95.214.181.110
32 2026-08-25 11:32 639232535349285207
473 ms 95.214.181.110
31 2026-08-25 11:15 639232524938080723
485 ms 95.214.181.110
30 2026-08-25 10:21 639232492740373468
3 ms 95.214.181.110
29 2026-08-25 10:04 639232482235303141
5 ms 95.214.181.110
28 2026-08-25 09:46 639232471861770303
241 ms 95.214.181.110
27 2026-08-25 09:29 639232461630217327
8 ms 95.214.181.110
26 2026-08-25 09:12 639232451282965990
4 ms 95.214.181.110
25 2026-08-25 08:54 639232440814614938
5 ms 95.214.181.110
24 2026-08-25 08:37 639232430410720425
16 ms 95.214.181.110
23 2026-08-25 08:20 639232420003096185
496 ms 95.214.181.110
22 2026-08-25 08:02 639232409467287444
249 ms 95.214.181.110
21 2026-08-25 07:45 639232399077195997
481 ms 95.214.181.110
20 2026-08-25 07:27 639232388731528337
477 ms 95.214.181.110
19 2026-08-25 07:10 639232378288598612
4 ms 95.214.181.110
18 2026-08-25 06:16 639232346196373643
3 ms 95.214.181.110
17 2026-08-25 06:00 639232336112370741
2 ms 95.214.181.110
16 2026-08-25 05:43 639232326146508970
3 ms 95.214.181.110
15 2026-08-25 05:26 639232316189381720
288 ms 95.214.181.110
14 2026-08-25 05:10 639232306217998913
3 ms 95.214.181.110
13 2026-08-25 04:53 639232296255744174
3 ms 95.214.181.110
12 2026-08-25 04:36 639232286095760789
3 ms 95.214.181.110
11 2026-08-25 04:19 639232276086186273
478 ms 95.214.181.110
10 2026-08-25 04:03 639232265900986425
248 ms 95.214.181.110
9 2026-08-25 03:46 639232255723518075
241 ms 95.214.181.110
8 2026-08-25 03:29 639232245484452890
479 ms 95.214.181.110
7 2026-08-25 03:12 639232235157175331
477 ms 95.214.181.110
6 2026-08-25 02:18 639232203197189095
473 ms 95.214.181.110
5 2026-08-25 02:01 639232192844564298
481 ms 95.214.181.110
4 2026-08-25 01:44 639232182496008942
470 ms 95.214.181.110
3 2026-08-25 01:26 639232172197053132
2 ms 95.214.181.110
2 2026-08-25 00:33 639232140250307418
3 ms 95.214.181.110
1 2026-08-25 00:16 639232129927860324
470 ms 95.214.181.110