DNS response history for id1.teamworks.my.id

id1.teamworks.my.id 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 31 DNS check records, 31 successful responses, 0 failed responses, and 363 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 id1.teamworks.my.id.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

363 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:53

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.20.190.80

Most recently resolved hosting IP on selected date

Successful Responses

31

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 id1.teamworks.my.id

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
31 2026-08-26 09:53 639233339545274518
361 ms 103.20.190.80
30 2026-08-26 09:35 639233329214918079
1677 ms 103.20.190.80
29 2026-08-26 09:18 639233318749762337
272 ms 103.20.190.80
28 2026-08-26 09:01 639233308387917838
116 ms 103.20.190.80
27 2026-08-26 08:43 639233297961740122
343 ms 103.20.190.80
26 2026-08-26 08:26 639233287487159094
245 ms 103.20.190.80
25 2026-08-26 08:09 639233276995531707
330 ms 103.20.190.80
24 2026-08-26 07:51 639233266521568229
258 ms 103.20.190.80
23 2026-08-26 07:33 639233256081047431
298 ms 103.20.190.80
22 2026-08-26 06:39 639233223620132921
396 ms 103.20.190.80
21 2026-08-26 06:22 639233213287814244
244 ms 103.20.190.80
20 2026-08-26 06:05 639233202925983161
781 ms 103.20.190.80
19 2026-08-26 05:48 639233192644780696
173 ms 103.20.190.80
18 2026-08-26 05:30 639233182401183833
256 ms 103.20.190.80
17 2026-08-26 05:13 639233172074181051
613 ms 103.20.190.80
16 2026-08-26 04:56 639233161808421455
109 ms 103.20.190.80
15 2026-08-26 04:39 639233151357344052
110 ms 103.20.190.80
14 2026-08-26 04:22 639233141034116946
106 ms 103.20.190.80
13 2026-08-26 04:05 639233130828334142
112 ms 103.20.190.80
12 2026-08-26 03:47 639233120373450007
161 ms 103.20.190.80
11 2026-08-26 03:30 639233110066216193
902 ms 103.20.190.80
10 2026-08-26 02:37 639233078065410564
223 ms 103.20.190.80
9 2026-08-26 02:20 639233067787457832
109 ms 103.20.190.80
8 2026-08-26 02:02 639233057501801162
315 ms 103.20.190.80
7 2026-08-26 01:45 639233047089431703
217 ms 103.20.190.80
6 2026-08-26 01:28 639233036754790688
1817 ms 103.20.190.80
5 2026-08-26 01:11 639233026412602472
110 ms 103.20.190.80
4 2026-08-26 00:53 639233016064066127
110 ms 103.20.190.80
3 2026-08-26 00:36 639233005922655772
262 ms 103.20.190.80
2 2026-08-26 00:19 639232995672256907
109 ms 103.20.190.80
1 2026-08-26 00:02 639232985300872416
108 ms 103.20.190.80