You don't, or at least you can do anything about it. From the results here it looks to be an eastern issue. From a command prompt or terminal you can try "ping forum.expeditionportal.com" and see if that works, and if you resolve the IP (I'm getting 50.28.25.200 from CO and TX). If you can resolve the IP then it's not a DNS update and caching issue and is a problem along the route. In that case ou can also try "tracert 50.28.25.200" (that's on Windows, use "traceroute 50.28.25.200" on MacOS/Linux). You won't be able to actually DO anything, but it will show where along the path the problem lies.
For example here is my traceroute result once I get upstream of my ISP:
11 lw-dc3-core1-eth2-19.rtr.liquidweb.com (209.59.157.244) 41.621 ms 40.547 ms 42.435 ms
12 lw-dc3-dist8-po5.rtr.liquidweb.com (69.167.128.133) 41.780 ms 42.444 ms 40.360 ms
13 w1.expeditionportal.com (50.28.25.200) 42.884 ms 41.367 ms 42.532 ms