DNS response history for ns2.paysteroid.com

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

28

Historical checks stored for this nameserver on selected date

Average Latency

234 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

160.153.177.118

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 ns2.paysteroid.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
28 2026-08-26 08:58 639233308387917838
171 ms 160.153.177.118
27 2026-08-26 08:41 639233297961740122
314 ms 160.153.177.118
26 2026-08-26 08:24 639233287487159094
317 ms 160.153.177.118
25 2026-08-26 08:06 639233276995531707
314 ms 160.153.177.118
24 2026-08-26 07:49 639233266521568229
312 ms 160.153.177.118
23 2026-08-26 07:31 639233256081047431
155 ms 160.153.177.118
22 2026-08-26 06:37 639233223620132921
31 ms 160.153.177.118
21 2026-08-26 06:20 639233213287814244
314 ms 160.153.177.118
20 2026-08-26 06:03 639233202925983161
184 ms 160.153.177.118
19 2026-08-26 05:45 639233192644780696
309 ms 160.153.177.118
18 2026-08-26 05:28 639233182401183833
314 ms 160.153.177.118
17 2026-08-26 05:11 639233172074181051
32 ms 160.153.177.118
16 2026-08-26 04:54 639233161808421455
325 ms 160.153.177.118
15 2026-08-26 04:37 639233151357344052
304 ms 160.153.177.118
14 2026-08-26 04:19 639233141034116946
306 ms 160.153.177.118
13 2026-08-26 04:02 639233130828334142
156 ms 160.153.177.118
12 2026-08-26 03:45 639233120373450007
314 ms 160.153.177.118
11 2026-08-26 03:28 639233110066216193
331 ms 160.153.177.118
10 2026-08-26 02:35 639233078065410564
289 ms 160.153.177.118
9 2026-08-26 02:17 639233067787457832
10 ms 160.153.177.118
8 2026-08-26 02:00 639233057501801162
185 ms 160.153.177.118
7 2026-08-26 01:43 639233047089431703
307 ms 160.153.177.118
6 2026-08-26 01:26 639233036754790688
156 ms 160.153.177.118
5 2026-08-26 01:09 639233026412602472
313 ms 160.153.177.118
4 2026-08-26 00:51 639233016064066127
157 ms 160.153.177.118
3 2026-08-26 00:34 639233005922655772
158 ms 160.153.177.118
2 2026-08-26 00:17 639232995672256907
311 ms 160.153.177.118
1 2026-08-26 00:00 639232985300872416
156 ms 160.153.177.118