DNS response history for dns02.nobilitypm.com

dns02.nobilitypm.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-31. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 192 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 dns02.nobilitypm.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

192 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-31 12:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

72.28.112.202

Most recently resolved hosting IP on selected date

Successful Responses

37

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 dns02.nobilitypm.com

Showing DNS history for 2026-08-31 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
37 2026-08-31 12:10 639237742927117371
275 ms 72.28.112.202
36 2026-08-31 11:52 639237732538256235
262 ms 72.28.112.202
35 2026-08-31 11:35 639237722025682013
245 ms 72.28.112.202
34 2026-08-31 11:17 639237711568720101
274 ms 72.28.112.202
33 2026-08-31 11:00 639237701119461876
256 ms 72.28.112.202
32 2026-08-31 10:42 639237690759595513
265 ms 72.28.112.202
31 2026-08-31 10:25 639237680122296836
276 ms 72.28.112.202
30 2026-08-31 09:31 639237647999458954
252 ms 72.28.112.202
29 2026-08-31 09:14 639237637680951774
266 ms 72.28.112.202
28 2026-08-31 08:57 639237627437728712
256 ms 72.28.112.202
27 2026-08-31 08:40 639237617127808241
12 ms 72.28.112.202
26 2026-08-31 08:23 639237606990101394
274 ms 72.28.112.202
25 2026-08-31 08:06 639237596595480036
8 ms 72.28.112.202
24 2026-08-31 07:49 639237586261012001
269 ms 72.28.112.202
23 2026-08-31 07:31 639237576047657695
251 ms 72.28.112.202
22 2026-08-31 07:14 639237565832936443
279 ms 72.28.112.202
21 2026-08-31 06:57 639237555466329546
160 ms 72.28.112.202
20 2026-08-31 06:40 639237545032411072
310 ms 72.28.112.202
19 2026-08-31 06:22 639237534469438634
256 ms 72.28.112.202
18 2026-08-31 05:28 639237502279296801
157 ms 72.28.112.202
17 2026-08-31 05:12 639237492362730124
262 ms 72.28.112.202
16 2026-08-31 04:55 639237482311584319
280 ms 72.28.112.202
15 2026-08-31 04:38 639237472150685594
21 ms 72.28.112.202
14 2026-08-31 04:21 639237462055295430
10 ms 72.28.112.202
13 2026-08-31 04:05 639237452089913890
4 ms 72.28.112.202
12 2026-08-31 03:48 639237441972654103
146 ms 72.28.112.202
11 2026-08-31 03:31 639237432052396478
258 ms 72.28.112.202
10 2026-08-31 03:15 639237422012990851
4 ms 72.28.112.202
9 2026-08-31 02:58 639237411889602012
13 ms 72.28.112.202
8 2026-08-31 02:41 639237401637354221
177 ms 72.28.112.202
7 2026-08-31 02:24 639237391412690360
8 ms 72.28.112.202
6 2026-08-31 01:31 639237359972957132
267 ms 72.28.112.202
5 2026-08-31 01:15 639237350032183979
272 ms 72.28.112.202
4 2026-08-31 00:58 639237340111452066
262 ms 72.28.112.202
3 2026-08-31 00:41 639237329967272514
3 ms 72.28.112.202
2 2026-08-31 00:24 639237319916508151
256 ms 72.28.112.202
1 2026-08-31 00:08 639237309944877243
257 ms 72.28.112.202