DNS response history for ns3.iforte.net.id

ns3.iforte.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 28 DNS check records, 28 successful responses, 0 failed responses, and 153 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 ns3.iforte.net.id.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

153 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.51.104.3

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 ns3.iforte.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
28 2026-08-25 09:43 639232471861770303
161 ms 202.51.104.3
27 2026-08-25 09:26 639232461630217327
163 ms 202.51.104.3
26 2026-08-25 09:08 639232451282965990
162 ms 202.51.104.3
25 2026-08-25 08:51 639232440814614938
173 ms 202.51.104.3
24 2026-08-25 08:34 639232430410720425
162 ms 202.51.104.3
23 2026-08-25 08:16 639232420003096185
324 ms 202.51.104.3
22 2026-08-25 07:59 639232409467287444
162 ms 202.51.104.3
21 2026-08-25 07:41 639232399077195997
161 ms 202.51.104.3
20 2026-08-25 07:24 639232388731528337
4 ms 202.51.104.3
19 2026-08-25 07:07 639232378288598612
335 ms 202.51.104.3
18 2026-08-25 06:13 639232346196373643
328 ms 202.51.104.3
17 2026-08-25 05:56 639232336112370741
2 ms 202.51.104.3
16 2026-08-25 05:40 639232326146508970
166 ms 202.51.104.3
15 2026-08-25 05:23 639232316189381720
160 ms 202.51.104.3
14 2026-08-25 05:07 639232306217998913
7 ms 202.51.104.3
13 2026-08-25 04:50 639232296255744174
165 ms 202.51.104.3
12 2026-08-25 04:33 639232286095760789
3 ms 202.51.104.3
11 2026-08-25 04:16 639232276086186273
3 ms 202.51.104.3
10 2026-08-25 03:59 639232265900986425
3 ms 202.51.104.3
9 2026-08-25 03:42 639232255723518075
161 ms 202.51.104.3
8 2026-08-25 03:25 639232245484452890
325 ms 202.51.104.3
7 2026-08-25 03:08 639232235157175331
163 ms 202.51.104.3
6 2026-08-25 02:15 639232203197189095
7 ms 202.51.104.3
5 2026-08-25 01:58 639232192844564298
160 ms 202.51.104.3
4 2026-08-25 01:40 639232182496008942
164 ms 202.51.104.3
3 2026-08-25 01:23 639232172197053132
326 ms 202.51.104.3
2 2026-08-25 00:30 639232140250307418
172 ms 202.51.104.3
1 2026-08-25 00:13 639232129927860324
162 ms 202.51.104.3