DNS response history for ns2.yellowbridge.com

ns2.yellowbridge.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 297 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.yellowbridge.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

297 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

172.96.180.47

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 ns2.yellowbridge.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:05 639232556111768563
330 ms 172.96.180.47
33 2026-08-25 11:48 639232545839529039
327 ms 172.96.180.47
32 2026-08-25 11:31 639232535349285207
326 ms 172.96.180.47
31 2026-08-25 11:13 639232524938080723
346 ms 172.96.180.47
30 2026-08-25 10:20 639232492740373468
172 ms 172.96.180.47
29 2026-08-25 10:03 639232482235303141
338 ms 172.96.180.47
28 2026-08-25 09:45 639232471861770303
174 ms 172.96.180.47
27 2026-08-25 09:28 639232461630217327
326 ms 172.96.180.47
26 2026-08-25 09:11 639232451282965990
332 ms 172.96.180.47
25 2026-08-25 08:53 639232440814614938
330 ms 172.96.180.47
24 2026-08-25 08:36 639232430410720425
334 ms 172.96.180.47
23 2026-08-25 08:19 639232420003096185
167 ms 172.96.180.47
22 2026-08-25 08:01 639232409467287444
333 ms 172.96.180.47
21 2026-08-25 07:44 639232399077195997
184 ms 172.96.180.47
20 2026-08-25 07:26 639232388731528337
334 ms 172.96.180.47
19 2026-08-25 07:09 639232378288598612
330 ms 172.96.180.47
18 2026-08-25 06:15 639232346196373643
337 ms 172.96.180.47
17 2026-08-25 05:58 639232336112370741
169 ms 172.96.180.47
16 2026-08-25 05:42 639232326146508970
162 ms 172.96.180.47
15 2026-08-25 05:25 639232316189381720
329 ms 172.96.180.47
14 2026-08-25 05:09 639232306217998913
333 ms 172.96.180.47
13 2026-08-25 04:52 639232296255744174
289 ms 172.96.180.47
12 2026-08-25 04:35 639232286095760789
328 ms 172.96.180.47
11 2026-08-25 04:18 639232276086186273
327 ms 172.96.180.47
10 2026-08-25 04:02 639232265900986425
330 ms 172.96.180.47
9 2026-08-25 03:45 639232255723518075
337 ms 172.96.180.47
8 2026-08-25 03:28 639232245484452890
327 ms 172.96.180.47
7 2026-08-25 03:10 639232235157175331
329 ms 172.96.180.47
6 2026-08-25 02:17 639232203197189095
165 ms 172.96.180.47
5 2026-08-25 02:00 639232192844564298
329 ms 172.96.180.47
4 2026-08-25 01:43 639232182496008942
322 ms 172.96.180.47
3 2026-08-25 01:25 639232172197053132
341 ms 172.96.180.47
2 2026-08-25 00:32 639232140250307418
330 ms 172.96.180.47
1 2026-08-25 00:15 639232129927860324
326 ms 172.96.180.47