DNS response history for bow2.djibtel.dj

bow2.djibtel.dj 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 342 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 bow2.djibtel.dj.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

342 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

196.201.196.40

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 bow2.djibtel.dj

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:05 639232556111768563
86 ms 196.201.196.40
33 2026-08-25 11:48 639232545839529039
5 ms 196.201.196.40
32 2026-08-25 11:31 639232535349285207
83 ms 196.201.196.40
31 2026-08-25 11:13 639232524938080723
537 ms 196.201.196.40
30 2026-08-25 10:20 639232492740373468
79 ms 196.201.196.40
29 2026-08-25 10:03 639232482235303141
139 ms 196.201.196.40
28 2026-08-25 09:45 639232471861770303
141 ms 196.201.196.40
27 2026-08-25 09:28 639232461630217327
79 ms 196.201.196.40
26 2026-08-25 09:11 639232451282965990
493 ms 196.201.196.40
25 2026-08-25 08:53 639232440814614938
143 ms 196.201.196.40
24 2026-08-25 08:36 639232430410720425
9 ms 196.201.196.40
23 2026-08-25 08:19 639232420003096185
167 ms 196.201.196.40
22 2026-08-25 08:01 639232409467287444
4 ms 196.201.196.40
21 2026-08-25 07:44 639232399077195997
79 ms 196.201.196.40
20 2026-08-25 07:26 639232388731528337
94 ms 196.201.196.40
19 2026-08-25 07:09 639232378288598612
137 ms 196.201.196.40
18 2026-08-25 06:15 639232346196373643
2098 ms 196.201.196.40
17 2026-08-25 05:58 639232336112370741
139 ms 196.201.196.40
16 2026-08-25 05:42 639232326146508970
3 ms 196.201.196.40
15 2026-08-25 05:25 639232316189381720
80 ms 196.201.196.40
14 2026-08-25 05:09 639232306217998913
5 ms 196.201.196.40
13 2026-08-25 04:52 639232296255744174
82 ms 196.201.196.40
12 2026-08-25 04:35 639232286095760789
1262 ms 196.201.196.40
11 2026-08-25 04:18 639232276086186273
134 ms 196.201.196.40
10 2026-08-25 04:02 639232265900986425
77 ms 196.201.196.40
9 2026-08-25 03:45 639232255723518075
79 ms 196.201.196.40
8 2026-08-25 03:28 639232245484452890
527 ms 196.201.196.40
7 2026-08-25 03:10 639232235157175331
78 ms 196.201.196.40
6 2026-08-25 02:17 639232203197189095
2299 ms 196.201.196.40
5 2026-08-25 02:00 639232192844564298
78 ms 196.201.196.40
4 2026-08-25 01:43 639232182496008942
153 ms 196.201.196.40
3 2026-08-25 01:25 639232172197053132
132 ms 196.201.196.40
2 2026-08-25 00:32 639232140250307418
135 ms 196.201.196.40
1 2026-08-25 00:15 639232129927860324
2008 ms 196.201.196.40