DNS response history for ns2.boygebd.com

ns2.boygebd.com 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 27 DNS check records, 27 successful responses, 0 failed responses, and 440 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 ns2.boygebd.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

440 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.112.62.71

Most recently resolved hosting IP on selected date

Successful Responses

27

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 ns2.boygebd.com

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
27 2026-08-25 09:28 639232461630217327
379 ms 103.112.62.71
26 2026-08-25 09:11 639232451282965990
190 ms 103.112.62.71
25 2026-08-25 08:54 639232440814614938
390 ms 103.112.62.71
24 2026-08-25 08:37 639232430410720425
372 ms 103.112.62.71
23 2026-08-25 08:19 639232420003096185
368 ms 103.112.62.71
22 2026-08-25 08:02 639232409467287444
2194 ms 103.112.62.71
21 2026-08-25 07:44 639232399077195997
360 ms 103.112.62.71
20 2026-08-25 07:27 639232388731528337
381 ms 103.112.62.71
19 2026-08-25 07:10 639232378288598612
357 ms 103.112.62.71
18 2026-08-25 06:16 639232346196373643
374 ms 103.112.62.71
17 2026-08-25 05:59 639232336112370741
368 ms 103.112.62.71
16 2026-08-25 05:42 639232326146508970
182 ms 103.112.62.71
15 2026-08-25 05:26 639232316189381720
367 ms 103.112.62.71
14 2026-08-25 05:09 639232306217998913
371 ms 103.112.62.71
13 2026-08-25 04:53 639232296255744174
4 ms 103.112.62.71
12 2026-08-25 04:36 639232286095760789
386 ms 103.112.62.71
11 2026-08-25 04:19 639232276086186273
173 ms 103.112.62.71
10 2026-08-25 04:02 639232265900986425
2181 ms 103.112.62.71
9 2026-08-25 03:45 639232255723518075
380 ms 103.112.62.71
8 2026-08-25 03:28 639232245484452890
190 ms 103.112.62.71
7 2026-08-25 03:11 639232235157175331
182 ms 103.112.62.71
6 2026-08-25 02:18 639232203197189095
189 ms 103.112.62.71
5 2026-08-25 02:01 639232192844564298
408 ms 103.112.62.71
4 2026-08-25 01:43 639232182496008942
374 ms 103.112.62.71
3 2026-08-25 01:26 639232172197053132
366 ms 103.112.62.71
2 2026-08-25 00:33 639232140250307418
3 ms 103.112.62.71
1 2026-08-25 00:16 639232129927860324
381 ms 103.112.62.71