DNS response history for ns1.heishin.mobi

ns1.heishin.mobi 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-26. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 550 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.heishin.mobi.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

550 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

101.143.229.178

Most recently resolved hosting IP on selected date

Successful Responses

28

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.heishin.mobi

Showing DNS history for 2026-08-26 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
28 2026-08-26 09:00 639233308387917838
552 ms 101.143.229.178
27 2026-08-26 08:43 639233297961740122
687 ms 101.143.229.178
26 2026-08-26 08:25 639233287487159094
270 ms 101.143.229.178
25 2026-08-26 08:08 639233276995531707
541 ms 101.143.229.178
24 2026-08-26 07:50 639233266521568229
359 ms 101.143.229.178
23 2026-08-26 07:33 639233256081047431
780 ms 101.143.229.178
22 2026-08-26 06:39 639233223620132921
529 ms 101.143.229.178
21 2026-08-26 06:22 639233213287814244
3 ms 101.143.229.178
20 2026-08-26 06:04 639233202925983161
2262 ms 101.143.229.178
19 2026-08-26 05:47 639233192644780696
290 ms 101.143.229.178
18 2026-08-26 05:30 639233182401183833
535 ms 101.143.229.178
17 2026-08-26 05:13 639233172074181051
781 ms 101.143.229.178
16 2026-08-26 04:56 639233161808421455
5 ms 101.143.229.178
15 2026-08-26 04:39 639233151357344052
3 ms 101.143.229.178
14 2026-08-26 04:21 639233141034116946
563 ms 101.143.229.178
13 2026-08-26 04:04 639233130828334142
657 ms 101.143.229.178
12 2026-08-26 03:47 639233120373450007
274 ms 101.143.229.178
11 2026-08-26 03:30 639233110066216193
553 ms 101.143.229.178
10 2026-08-26 02:36 639233078065410564
701 ms 101.143.229.178
9 2026-08-26 02:19 639233067787457832
553 ms 101.143.229.178
8 2026-08-26 02:02 639233057501801162
558 ms 101.143.229.178
7 2026-08-26 01:45 639233047089431703
2 ms 101.143.229.178
6 2026-08-26 01:28 639233036754790688
274 ms 101.143.229.178
5 2026-08-26 01:10 639233026412602472
667 ms 101.143.229.178
4 2026-08-26 00:53 639233016064066127
787 ms 101.143.229.178
3 2026-08-26 00:36 639233005922655772
820 ms 101.143.229.178
2 2026-08-26 00:19 639232995672256907
784 ms 101.143.229.178
1 2026-08-26 00:02 639232985300872416
611 ms 101.143.229.178