DNS response history for ns1.bigemilang.net

ns1.bigemilang.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-26. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 775 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.bigemilang.net.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

775 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.67.48.6

Most recently resolved hosting IP on selected date

Successful Responses

38

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.bigemilang.net

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
38 2026-08-26 12:33 639233434974187439
173 ms 103.67.48.6
37 2026-08-26 12:16 639233424567558554
169 ms 103.67.48.6
36 2026-08-26 11:59 639233414056832719
1300 ms 103.67.48.6
35 2026-08-26 11:41 639233403515141099
167 ms 103.67.48.6
34 2026-08-26 10:46 639233370841350248
803 ms 103.67.48.6
33 2026-08-26 10:29 639233360361507238
782 ms 103.67.48.6
32 2026-08-26 10:12 639233350067824371
1207 ms 103.67.48.6
31 2026-08-26 09:55 639233339545274518
167 ms 103.67.48.6
30 2026-08-26 09:37 639233329214918079
167 ms 103.67.48.6
29 2026-08-26 09:20 639233318749762337
169 ms 103.67.48.6
28 2026-08-26 09:02 639233308387917838
766 ms 103.67.48.6
27 2026-08-26 08:45 639233297961740122
168 ms 103.67.48.6
26 2026-08-26 08:28 639233287487159094
1263 ms 103.67.48.6
25 2026-08-26 08:10 639233276995531707
768 ms 103.67.48.6
24 2026-08-26 07:53 639233266521568229
1203 ms 103.67.48.6
23 2026-08-26 07:35 639233256081047431
168 ms 103.67.48.6
22 2026-08-26 06:41 639233223620132921
1187 ms 103.67.48.6
21 2026-08-26 06:24 639233213287814244
767 ms 103.67.48.6
20 2026-08-26 06:07 639233202925983161
1272 ms 103.67.48.6
19 2026-08-26 05:49 639233192644780696
174 ms 103.67.48.6
18 2026-08-26 05:32 639233182401183833
763 ms 103.67.48.6
17 2026-08-26 05:15 639233172074181051
1853 ms 103.67.48.6
16 2026-08-26 04:58 639233161808421455
1188 ms 103.67.48.6
15 2026-08-26 04:41 639233151357344052
1297 ms 103.67.48.6
14 2026-08-26 04:23 639233141034116946
901 ms 103.67.48.6
13 2026-08-26 04:06 639233130828334142
770 ms 103.67.48.6
12 2026-08-26 03:49 639233120373450007
165 ms 103.67.48.6
11 2026-08-26 03:32 639233110066216193
771 ms 103.67.48.6
10 2026-08-26 02:38 639233078065410564
919 ms 103.67.48.6
9 2026-08-26 02:21 639233067787457832
782 ms 103.67.48.6
8 2026-08-26 02:04 639233057501801162
992 ms 103.67.48.6
7 2026-08-26 01:47 639233047089431703
1229 ms 103.67.48.6
6 2026-08-26 01:30 639233036754790688
1186 ms 103.67.48.6
5 2026-08-26 01:12 639233026412602472
167 ms 103.67.48.6
4 2026-08-26 00:55 639233016064066127
1187 ms 103.67.48.6
3 2026-08-26 00:38 639233005922655772
1031 ms 103.67.48.6
2 2026-08-26 00:21 639232995672256907
174 ms 103.67.48.6
1 2026-08-26 00:04 639232985300872416
1222 ms 103.67.48.6