DNS response history for ns4.nirbhor.com

ns4.nirbhor.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 28 DNS check records, 28 successful responses, 0 failed responses, and 22 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 ns4.nirbhor.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

22 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

134.199.163.159

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 ns4.nirbhor.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
28 2026-08-27 09:02 639234181105879568
18 ms 134.199.163.159
27 2026-08-27 08:45 639234170713214496
24 ms 134.199.163.159
26 2026-08-27 08:28 639234160341037652
24 ms 134.199.163.159
25 2026-08-27 08:10 639234149799404224
36 ms 134.199.163.159
24 2026-08-27 07:53 639234139553286469
18 ms 134.199.163.159
23 2026-08-27 06:59 639234107183588293
15 ms 134.199.163.159
22 2026-08-27 06:42 639234096905435724
17 ms 134.199.163.159
21 2026-08-27 06:25 639234086579410775
20 ms 134.199.163.159
20 2026-08-27 06:08 639234076291157956
18 ms 134.199.163.159
19 2026-08-27 05:51 639234065981939454
36 ms 134.199.163.159
18 2026-08-27 05:33 639234055548642997
10 ms 134.199.163.159
17 2026-08-27 05:16 639234045267979603
32 ms 134.199.163.159
16 2026-08-27 04:59 639234034999717463
28 ms 134.199.163.159
15 2026-08-27 04:42 639234024739225358
16 ms 134.199.163.159
14 2026-08-27 04:24 639234014311170162
24 ms 134.199.163.159
13 2026-08-27 04:07 639234003806017640
20 ms 134.199.163.159
12 2026-08-27 03:49 639233993356203030
30 ms 134.199.163.159
11 2026-08-27 02:56 639233961301716608
17 ms 134.199.163.159
10 2026-08-27 02:39 639233950834200647
19 ms 134.199.163.159
9 2026-08-27 02:21 639233940431849026
21 ms 134.199.163.159
8 2026-08-27 02:04 639233930110596398
28 ms 134.199.163.159
7 2026-08-27 01:47 639233919705434540
9 ms 134.199.163.159
6 2026-08-27 01:30 639233909452807845
30 ms 134.199.163.159
5 2026-08-27 01:12 639233899096420820
17 ms 134.199.163.159
4 2026-08-27 00:55 639233888707824939
16 ms 134.199.163.159
3 2026-08-27 00:38 639233878461203802
20 ms 134.199.163.159
2 2026-08-27 00:21 639233868060868209
18 ms 134.199.163.159
1 2026-08-27 00:03 639233857450922991
47 ms 134.199.163.159