DNS response history for ns2.recombat.com

ns2.recombat.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-30. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 368 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.recombat.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

368 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 10:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

218.145.65.144

Most recently resolved hosting IP on selected date

Successful Responses

31

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

Showing DNS history for 2026-08-30 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
31 2026-08-30 10:29 639236817708615077
567 ms 218.145.65.144
30 2026-08-30 09:36 639236785770651804
506 ms 218.145.65.144
29 2026-08-30 09:19 639236775820686373
558 ms 218.145.65.144
28 2026-08-30 09:03 639236765768339082
4 ms 218.145.65.144
27 2026-08-30 08:46 639236755602384085
564 ms 218.145.65.144
26 2026-08-30 08:29 639236745600094925
556 ms 218.145.65.144
25 2026-08-30 08:12 639236735311262753
487 ms 218.145.65.144
24 2026-08-30 07:55 639236724996745235
569 ms 218.145.65.144
23 2026-08-30 07:38 639236714839899761
291 ms 218.145.65.144
22 2026-08-30 07:21 639236704748431488
567 ms 218.145.65.144
21 2026-08-30 07:04 639236694430128550
3 ms 218.145.65.144
20 2026-08-30 06:47 639236684143292417
564 ms 218.145.65.144
19 2026-08-30 06:30 639236673972499943
568 ms 218.145.65.144
18 2026-08-30 05:36 639236642126522802
284 ms 218.145.65.144
17 2026-08-30 05:20 639236632183518198
2 ms 218.145.65.144
16 2026-08-30 05:03 639236622289312589
567 ms 218.145.65.144
15 2026-08-30 04:47 639236612490676525
278 ms 218.145.65.144
14 2026-08-30 04:30 639236602582494852
3 ms 218.145.65.144
13 2026-08-30 04:14 639236592511706469
276 ms 218.145.65.144
12 2026-08-30 03:57 639236582441006869
4 ms 218.145.65.144
11 2026-08-30 03:40 639236572478785089
562 ms 218.145.65.144
10 2026-08-30 03:24 639236562556749999
276 ms 218.145.65.144
9 2026-08-30 03:07 639236552353482281
286 ms 218.145.65.144
8 2026-08-30 02:50 639236542188881607
3 ms 218.145.65.144
7 2026-08-30 02:33 639236531885440105
587 ms 218.145.65.144
6 2026-08-30 01:39 639236499922985383
280 ms 218.145.65.144
5 2026-08-30 01:23 639236489713594431
565 ms 218.145.65.144
4 2026-08-30 01:06 639236479750443901
574 ms 218.145.65.144
3 2026-08-30 00:49 639236469719936375
3 ms 218.145.65.144
2 2026-08-30 00:32 639236459579244885
497 ms 218.145.65.144
1 2026-08-30 00:16 639236449582837549
565 ms 218.145.65.144