DNS response history for borobudur.ntt.net.id

borobudur.ntt.net.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-25. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 357 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 borobudur.ntt.net.id.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

357 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.171.1.3

Most recently resolved hosting IP on selected date

Successful Responses

34

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 borobudur.ntt.net.id

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
34 2026-08-25 12:04 639232556111768563
347 ms 202.171.1.3
33 2026-08-25 11:47 639232545839529039
337 ms 202.171.1.3
32 2026-08-25 11:30 639232535349285207
328 ms 202.171.1.3
31 2026-08-25 11:12 639232524938080723
327 ms 202.171.1.3
30 2026-08-25 10:18 639232492740373468
330 ms 202.171.1.3
29 2026-08-25 10:01 639232482235303141
333 ms 202.171.1.3
28 2026-08-25 09:44 639232471861770303
334 ms 202.171.1.3
27 2026-08-25 09:27 639232461630217327
196 ms 202.171.1.3
26 2026-08-25 09:09 639232451282965990
7 ms 202.171.1.3
25 2026-08-25 08:52 639232440814614938
188 ms 202.171.1.3
24 2026-08-25 08:35 639232430410720425
335 ms 202.171.1.3
23 2026-08-25 08:17 639232420003096185
201 ms 202.171.1.3
22 2026-08-25 08:00 639232409467287444
335 ms 202.171.1.3
21 2026-08-25 07:42 639232399077195997
341 ms 202.171.1.3
20 2026-08-25 07:25 639232388731528337
2010 ms 202.171.1.3
19 2026-08-25 07:08 639232378288598612
204 ms 202.171.1.3
18 2026-08-25 06:14 639232346196373643
341 ms 202.171.1.3
17 2026-08-25 05:57 639232336112370741
328 ms 202.171.1.3
16 2026-08-25 05:41 639232326146508970
198 ms 202.171.1.3
15 2026-08-25 05:24 639232316189381720
4 ms 202.171.1.3
14 2026-08-25 05:07 639232306217998913
329 ms 202.171.1.3
13 2026-08-25 04:51 639232296255744174
181 ms 202.171.1.3
12 2026-08-25 04:34 639232286095760789
172 ms 202.171.1.3
11 2026-08-25 04:17 639232276086186273
335 ms 202.171.1.3
10 2026-08-25 04:00 639232265900986425
3 ms 202.171.1.3
9 2026-08-25 03:43 639232255723518075
8 ms 202.171.1.3
8 2026-08-25 03:26 639232245484452890
323 ms 202.171.1.3
7 2026-08-25 03:09 639232235157175331
334 ms 202.171.1.3
6 2026-08-25 02:16 639232203197189095
338 ms 202.171.1.3
5 2026-08-25 01:59 639232192844564298
334 ms 202.171.1.3
4 2026-08-25 01:41 639232182496008942
331 ms 202.171.1.3
3 2026-08-25 01:24 639232172197053132
2222 ms 202.171.1.3
2 2026-08-25 00:31 639232140250307418
191 ms 202.171.1.3
1 2026-08-25 00:14 639232129927860324
3 ms 202.171.1.3