DNS response history for hold2.longming.com

hold2.longming.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 34 DNS check records, 34 successful responses, 0 failed responses, and 382 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 hold2.longming.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

382 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

218.95.37.215

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 hold2.longming.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
34 2026-08-25 12:06 639232556111768563
339 ms 218.95.37.215
33 2026-08-25 11:49 639232545839529039
343 ms 218.95.37.215
32 2026-08-25 11:31 639232535349285207
348 ms 218.95.37.215
31 2026-08-25 11:14 639232524938080723
329 ms 218.95.37.215
30 2026-08-25 10:20 639232492740373468
352 ms 218.95.37.215
29 2026-08-25 10:03 639232482235303141
339 ms 218.95.37.215
28 2026-08-25 09:45 639232471861770303
338 ms 218.95.37.215
27 2026-08-25 09:28 639232461630217327
352 ms 218.95.37.215
26 2026-08-25 09:11 639232451282965990
322 ms 218.95.37.215
25 2026-08-25 08:54 639232440814614938
351 ms 218.95.37.215
24 2026-08-25 08:36 639232430410720425
164 ms 218.95.37.215
23 2026-08-25 08:19 639232420003096185
343 ms 218.95.37.215
22 2026-08-25 08:02 639232409467287444
432 ms 218.95.37.215
21 2026-08-25 07:44 639232399077195997
328 ms 218.95.37.215
20 2026-08-25 07:27 639232388731528337
343 ms 218.95.37.215
19 2026-08-25 07:09 639232378288598612
350 ms 218.95.37.215
18 2026-08-25 06:16 639232346196373643
338 ms 218.95.37.215
17 2026-08-25 05:59 639232336112370741
420 ms 218.95.37.215
16 2026-08-25 05:42 639232326146508970
339 ms 218.95.37.215
15 2026-08-25 05:26 639232316189381720
330 ms 218.95.37.215
14 2026-08-25 05:09 639232306217998913
322 ms 218.95.37.215
13 2026-08-25 04:53 639232296255744174
327 ms 218.95.37.215
12 2026-08-25 04:36 639232286095760789
325 ms 218.95.37.215
11 2026-08-25 04:19 639232276086186273
342 ms 218.95.37.215
10 2026-08-25 04:02 639232265900986425
328 ms 218.95.37.215
9 2026-08-25 03:45 639232255723518075
336 ms 218.95.37.215
8 2026-08-25 03:28 639232245484452890
328 ms 218.95.37.215
7 2026-08-25 03:11 639232235157175331
165 ms 218.95.37.215
6 2026-08-25 02:18 639232203197189095
2020 ms 218.95.37.215
5 2026-08-25 02:01 639232192844564298
331 ms 218.95.37.215
4 2026-08-25 01:43 639232182496008942
350 ms 218.95.37.215
3 2026-08-25 01:26 639232172197053132
328 ms 218.95.37.215
2 2026-08-25 00:33 639232140250307418
338 ms 218.95.37.215
1 2026-08-25 00:16 639232129927860324
348 ms 218.95.37.215