DNS response history for c.nsmanage.net

c.nsmanage.net 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 27 DNS check records, 27 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 c.nsmanage.net.
Records on Selected Date

27

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-27 08:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.212.179.148

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 c.nsmanage.net

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
27 2026-08-27 08:58 639234170713214496
541 ms 49.212.179.148
26 2026-08-27 08:40 639234160341037652
269 ms 49.212.179.148
25 2026-08-27 08:23 639234149799404224
258 ms 49.212.179.148
24 2026-08-27 08:05 639234139553286469
271 ms 49.212.179.148
23 2026-08-27 07:12 639234107183588293
262 ms 49.212.179.148
22 2026-08-27 06:55 639234096905435724
259 ms 49.212.179.148
21 2026-08-27 06:38 639234086579410775
542 ms 49.212.179.148
20 2026-08-27 06:20 639234076291157956
272 ms 49.212.179.148
19 2026-08-27 06:03 639234065981939454
281 ms 49.212.179.148
18 2026-08-27 05:46 639234055548642997
272 ms 49.212.179.148
17 2026-08-27 05:29 639234045267979603
278 ms 49.212.179.148
16 2026-08-27 05:12 639234034999717463
274 ms 49.212.179.148
15 2026-08-27 04:54 639234024739225358
283 ms 49.212.179.148
14 2026-08-27 04:37 639234014311170162
560 ms 49.212.179.148
13 2026-08-27 04:20 639234003806017640
515 ms 49.212.179.148
12 2026-08-27 04:02 639233993356203030
274 ms 49.212.179.148
11 2026-08-27 03:09 639233961301716608
278 ms 49.212.179.148
10 2026-08-27 02:52 639233950834200647
281 ms 49.212.179.148
9 2026-08-27 02:34 639233940431849026
274 ms 49.212.179.148
8 2026-08-27 02:17 639233930110596398
281 ms 49.212.179.148
7 2026-08-27 02:00 639233919705434540
544 ms 49.212.179.148
6 2026-08-27 01:42 639233909452807845
525 ms 49.212.179.148
5 2026-08-27 01:25 639233899096420820
273 ms 49.212.179.148
4 2026-08-27 01:08 639233888707824939
277 ms 49.212.179.148
3 2026-08-27 00:51 639233878461203802
288 ms 49.212.179.148
2 2026-08-27 00:33 639233868060868209
277 ms 49.212.179.148
1 2026-08-27 00:16 639233857450922991
534 ms 49.212.179.148