DNS response history for ns2.modship.com

ns2.modship.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-25. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 475 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.modship.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

475 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.79.157.168

Most recently resolved hosting IP on selected date

Successful Responses

35

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

Showing DNS history for 2026-08-25 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
35 2026-08-25 12:22 639232566381512620
255 ms 51.79.157.168
34 2026-08-25 12:05 639232556111768563
328 ms 51.79.157.168
33 2026-08-25 11:48 639232545839529039
328 ms 51.79.157.168
32 2026-08-25 11:31 639232535349285207
420 ms 51.79.157.168
31 2026-08-25 11:13 639232524938080723
330 ms 51.79.157.168
30 2026-08-25 10:20 639232492740373468
324 ms 51.79.157.168
29 2026-08-25 10:02 639232482235303141
160 ms 51.79.157.168
28 2026-08-25 09:45 639232471861770303
321 ms 51.79.157.168
27 2026-08-25 09:28 639232461630217327
414 ms 51.79.157.168
26 2026-08-25 09:10 639232451282965990
923 ms 51.79.157.168
25 2026-08-25 08:53 639232440814614938
513 ms 51.79.157.168
24 2026-08-25 08:36 639232430410720425
320 ms 51.79.157.168
23 2026-08-25 08:18 639232420003096185
508 ms 51.79.157.168
22 2026-08-25 08:01 639232409467287444
160 ms 51.79.157.168
21 2026-08-25 07:44 639232399077195997
2007 ms 51.79.157.168
20 2026-08-25 07:26 639232388731528337
258 ms 51.79.157.168
19 2026-08-25 07:09 639232378288598612
158 ms 51.79.157.168
18 2026-08-25 06:15 639232346196373643
574 ms 51.79.157.168
17 2026-08-25 05:58 639232336112370741
3 ms 51.79.157.168
16 2026-08-25 05:42 639232326146508970
323 ms 51.79.157.168
15 2026-08-25 05:25 639232316189381720
3 ms 51.79.157.168
14 2026-08-25 05:09 639232306217998913
321 ms 51.79.157.168
13 2026-08-25 04:52 639232296255744174
349 ms 51.79.157.168
12 2026-08-25 04:35 639232286095760789
406 ms 51.79.157.168
11 2026-08-25 04:18 639232276086186273
160 ms 51.79.157.168
10 2026-08-25 04:01 639232265900986425
2351 ms 51.79.157.168
9 2026-08-25 03:45 639232255723518075
626 ms 51.79.157.168
8 2026-08-25 03:27 639232245484452890
330 ms 51.79.157.168
7 2026-08-25 03:10 639232235157175331
414 ms 51.79.157.168
6 2026-08-25 02:17 639232203197189095
490 ms 51.79.157.168
5 2026-08-25 02:00 639232192844564298
415 ms 51.79.157.168
4 2026-08-25 01:43 639232182496008942
638 ms 51.79.157.168
3 2026-08-25 01:25 639232172197053132
829 ms 51.79.157.168
2 2026-08-25 00:32 639232140250307418
322 ms 51.79.157.168
1 2026-08-25 00:15 639232129927860324
335 ms 51.79.157.168