DNS response history for ns2.providerlinkhealth.com

ns2.providerlinkhealth.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-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 319 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.providerlinkhealth.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

319 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.77.78.133

Most recently resolved hosting IP on selected date

Successful Responses

34

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.providerlinkhealth.com

Showing DNS history for 2026-08-26 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
34 2026-08-26 10:43 639233370841350248
567 ms 103.77.78.133
33 2026-08-26 10:26 639233360361507238
324 ms 103.77.78.133
32 2026-08-26 10:09 639233350067824371
179 ms 103.77.78.133
31 2026-08-26 09:52 639233339545274518
324 ms 103.77.78.133
30 2026-08-26 09:34 639233329214918079
326 ms 103.77.78.133
29 2026-08-26 09:17 639233318749762337
325 ms 103.77.78.133
28 2026-08-26 08:59 639233308387917838
342 ms 103.77.78.133
27 2026-08-26 08:42 639233297961740122
325 ms 103.77.78.133
26 2026-08-26 08:25 639233287487159094
327 ms 103.77.78.133
25 2026-08-26 08:07 639233276995531707
337 ms 103.77.78.133
24 2026-08-26 07:50 639233266521568229
339 ms 103.77.78.133
23 2026-08-26 07:32 639233256081047431
341 ms 103.77.78.133
22 2026-08-26 06:38 639233223620132921
324 ms 103.77.78.133
21 2026-08-26 06:21 639233213287814244
320 ms 103.77.78.133
20 2026-08-26 06:04 639233202925983161
325 ms 103.77.78.133
19 2026-08-26 05:46 639233192644780696
337 ms 103.77.78.133
18 2026-08-26 05:29 639233182401183833
207 ms 103.77.78.133
17 2026-08-26 05:12 639233172074181051
179 ms 103.77.78.133
16 2026-08-26 04:55 639233161808421455
328 ms 103.77.78.133
15 2026-08-26 04:38 639233151357344052
324 ms 103.77.78.133
14 2026-08-26 04:20 639233141034116946
324 ms 103.77.78.133
13 2026-08-26 04:03 639233130828334142
346 ms 103.77.78.133
12 2026-08-26 03:46 639233120373450007
326 ms 103.77.78.133
11 2026-08-26 03:29 639233110066216193
332 ms 103.77.78.133
10 2026-08-26 02:36 639233078065410564
325 ms 103.77.78.133
9 2026-08-26 02:18 639233067787457832
175 ms 103.77.78.133
8 2026-08-26 02:01 639233057501801162
325 ms 103.77.78.133
7 2026-08-26 01:44 639233047089431703
337 ms 103.77.78.133
6 2026-08-26 01:27 639233036754790688
347 ms 103.77.78.133
5 2026-08-26 01:10 639233026412602472
324 ms 103.77.78.133
4 2026-08-26 00:52 639233016064066127
207 ms 103.77.78.133
3 2026-08-26 00:35 639233005922655772
323 ms 103.77.78.133
2 2026-08-26 00:18 639232995672256907
325 ms 103.77.78.133
1 2026-08-26 00:01 639232985300872416
420 ms 103.77.78.133