DNS response history for ns2.transnagar.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

240 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

96.126.112.124

Most recently resolved hosting IP on selected date

Successful Responses

29

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.transnagar.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
29 2026-08-25 09:59 639232482235303141
123 ms 96.126.112.124
28 2026-08-25 09:41 639232471861770303
204 ms 96.126.112.124
27 2026-08-25 09:24 639232461630217327
125 ms 96.126.112.124
26 2026-08-25 09:07 639232451282965990
211 ms 96.126.112.124
25 2026-08-25 08:49 639232440814614938
147 ms 96.126.112.124
24 2026-08-25 08:32 639232430410720425
212 ms 96.126.112.124
23 2026-08-25 08:15 639232420003096185
207 ms 96.126.112.124
22 2026-08-25 07:57 639232409467287444
17 ms 96.126.112.124
21 2026-08-25 07:40 639232399077195997
208 ms 96.126.112.124
20 2026-08-25 07:22 639232388731528337
241 ms 96.126.112.124
19 2026-08-25 07:05 639232378288598612
209 ms 96.126.112.124
18 2026-08-25 06:12 639232346196373643
202 ms 96.126.112.124
17 2026-08-25 05:55 639232336112370741
209 ms 96.126.112.124
16 2026-08-25 05:38 639232326146508970
124 ms 96.126.112.124
15 2026-08-25 05:21 639232316189381720
9 ms 96.126.112.124
14 2026-08-25 05:05 639232306217998913
2032 ms 96.126.112.124
13 2026-08-25 04:48 639232296255744174
204 ms 96.126.112.124
12 2026-08-25 04:31 639232286095760789
124 ms 96.126.112.124
11 2026-08-25 04:15 639232276086186273
206 ms 96.126.112.124
10 2026-08-25 03:58 639232265900986425
203 ms 96.126.112.124
9 2026-08-25 03:41 639232255723518075
206 ms 96.126.112.124
8 2026-08-25 03:24 639232245484452890
132 ms 96.126.112.124
7 2026-08-25 03:07 639232235157175331
250 ms 96.126.112.124
6 2026-08-25 02:13 639232203197189095
204 ms 96.126.112.124
5 2026-08-25 01:56 639232192844564298
134 ms 96.126.112.124
4 2026-08-25 01:39 639232182496008942
205 ms 96.126.112.124
3 2026-08-25 01:22 639232172197053132
200 ms 96.126.112.124
2 2026-08-25 00:28 639232140250307418
199 ms 96.126.112.124
1 2026-08-25 00:11 639232129927860324
226 ms 96.126.112.124