DNS response history for ns2.wearemodel.com

ns2.wearemodel.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 258 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.wearemodel.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

258 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.170.190.139

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.wearemodel.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:07 639232556111768563
190 ms 203.170.190.139
34 2026-08-25 11:50 639232545839529039
190 ms 203.170.190.139
33 2026-08-25 11:33 639232535349285207
298 ms 203.170.190.139
32 2026-08-25 11:15 639232524938080723
299 ms 203.170.190.139
31 2026-08-25 10:22 639232492740373468
296 ms 203.170.190.139
30 2026-08-25 10:04 639232482235303141
188 ms 203.170.190.139
29 2026-08-25 09:47 639232471861770303
189 ms 203.170.190.139
28 2026-08-25 09:30 639232461630217327
291 ms 203.170.190.139
27 2026-08-25 09:13 639232451282965990
303 ms 203.170.190.139
26 2026-08-25 08:55 639232440814614938
299 ms 203.170.190.139
25 2026-08-25 08:38 639232430410720425
301 ms 203.170.190.139
24 2026-08-25 08:20 639232420003096185
187 ms 203.170.190.139
23 2026-08-25 08:03 639232409467287444
182 ms 203.170.190.139
22 2026-08-25 07:46 639232399077195997
296 ms 203.170.190.139
21 2026-08-25 07:28 639232388731528337
292 ms 203.170.190.139
20 2026-08-25 07:11 639232378288598612
191 ms 203.170.190.139
19 2026-08-25 06:17 639232346196373643
188 ms 203.170.190.139
18 2026-08-25 06:00 639232336112370741
296 ms 203.170.190.139
17 2026-08-25 05:44 639232326146508970
294 ms 203.170.190.139
16 2026-08-25 05:27 639232316189381720
198 ms 203.170.190.139
15 2026-08-25 05:11 639232306217998913
296 ms 203.170.190.139
14 2026-08-25 04:54 639232296255744174
181 ms 203.170.190.139
13 2026-08-25 04:37 639232286095760789
190 ms 203.170.190.139
12 2026-08-25 04:20 639232276086186273
295 ms 203.170.190.139
11 2026-08-25 04:03 639232265900986425
291 ms 203.170.190.139
10 2026-08-25 03:47 639232255723518075
314 ms 203.170.190.139
9 2026-08-25 03:29 639232245484452890
294 ms 203.170.190.139
8 2026-08-25 03:12 639232235157175331
116 ms 203.170.190.139
7 2026-08-25 02:19 639232203197189095
297 ms 203.170.190.139
6 2026-08-25 02:02 639232192844564298
300 ms 203.170.190.139
5 2026-08-25 01:45 639232182496008942
301 ms 203.170.190.139
4 2026-08-25 01:27 639232172197053132
292 ms 203.170.190.139
3 2026-08-25 00:34 639232140250307418
297 ms 203.170.190.139
2 2026-08-25 00:17 639232129927860324
294 ms 203.170.190.139
1 2026-08-25 00:00 639232119551972438
302 ms 203.170.190.139