DNS response history for ns2.nayeebrahminamarriage.com

ns2.nayeebrahminamarriage.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-27. For this date, NameServerHistory found 29 DNS check records, 28 successful responses, 1 failed responses, and 400 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.nayeebrahminamarriage.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

400 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.171.180.148

Most recently resolved hosting IP on selected date

Successful Responses

28

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.nayeebrahminamarriage.com

Showing DNS history for 2026-08-27 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-27 09:30 639234191649612722
188 ms 103.171.180.148
28 2026-08-27 09:13 639234181105879568
196 ms 103.171.180.148
27 2026-08-27 08:55 639234170713214496
568 ms 103.171.180.148
26 2026-08-27 08:38 639234160341037652
2227 ms 103.171.180.148
25 2026-08-27 08:20 639234149799404224
2147 ms 103.171.180.148
24 2026-08-27 08:03 639234139553286469
693 ms 103.171.180.148
23 2026-08-27 07:09 639234107183588293
267 ms 103.171.180.148
22 2026-08-27 06:52 639234096905435724
130 ms 103.171.180.148
21 2026-08-27 06:35 639234086579410775
159 ms 103.171.180.148
20 2026-08-27 06:18 639234076291157956
622 ms 103.171.180.148
19 2026-08-27 06:01 639234065981939454
291 ms 103.171.180.148
18 2026-08-27 05:44 639234055548642997
-
17 2026-08-27 05:26 639234045267979603
134 ms 103.171.180.148
16 2026-08-27 05:09 639234034999717463
139 ms 103.171.180.148
15 2026-08-27 04:52 639234024739225358
288 ms 103.171.180.148
14 2026-08-27 04:35 639234014311170162
136 ms 103.171.180.148
13 2026-08-27 04:17 639234003806017640
252 ms 103.171.180.148
12 2026-08-27 04:00 639233993356203030
262 ms 103.171.180.148
11 2026-08-27 03:06 639233961301716608
141 ms 103.171.180.148
10 2026-08-27 02:49 639233950834200647
269 ms 103.171.180.148
9 2026-08-27 02:31 639233940431849026
275 ms 103.171.180.148
8 2026-08-27 02:14 639233930110596398
138 ms 103.171.180.148
7 2026-08-27 01:57 639233919705434540
275 ms 103.171.180.148
6 2026-08-27 01:40 639233909452807845
172 ms 103.171.180.148
5 2026-08-27 01:22 639233899096420820
280 ms 103.171.180.148
4 2026-08-27 01:05 639233888707824939
136 ms 103.171.180.148
3 2026-08-27 00:48 639233878461203802
285 ms 103.171.180.148
2 2026-08-27 00:31 639233868060868209
264 ms 103.171.180.148
1 2026-08-27 00:13 639233857450922991
271 ms 103.171.180.148