• Follow us on Twitter @buckeyeplanet and @bp_recruiting, like us on Facebook! Enjoy a post or article, recommend it to others! BP is only as strong as its community, and we only promote by word of mouth, so share away!
  • Consider registering! Fewer and higher quality ads, no emails you don't want, access to all the forums, download game torrents, private messages, polls, Sportsbook, etc. Even if you just want to lurk, there are a lot of good reasons to register!

Fungo Squiggly

Mortal enemy of all things Bucky
Yahoo Pickem Champ
Former Game Champion
'18 BPCFFB II Champ
'18 Keeper League Champ
Just wondering if anyone else is having any problems accessing the site today?

No issues on mobile device but neither PC here has been able to reach the site. Both show a message of "resolving host" then report that the site is unavailable. Using Chrome, but have tried Firefox with similar results.

Neither a reboot nor a cleared cache has helped.

Thanks!
 
No issues here either. When running into this sort of thing you can run "cmd" on any Windows version and then type (and enter) "tracert www.buckeyeplanet.com". This will give you an idea of where the problem is. If you see asterisks before he.net, it's along the way. If you see them at he.net, it's within our network, and if you see them at www.buckeyeplanet.com, it's our box.

Here's mine:
C:\Users\Bryant>tracert www.buckeyeplanet.com

Tracing route to www.buckeyeplanet.com [2001:470:1:12d:230:0:3:0]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 2605:a000:(redacted)
2 17 ms 16 ms 18 ms 2605:a000:(redacted)
3 12 ms 10 ms 14 ms 2605:a000:(redacted)
4 15 ms 15 ms 11 ms 2605:a000:0:4::3:39e
5 22 ms 19 ms 19 ms 2605:a000:0:4::70
6 29 ms 28 ms 27 ms 2001:1998:0:4::1d0
7 28 ms 27 ms 36 ms 2001:1998:0:4::90
8 49 ms 25 ms 27 ms 2001:1998:0:4::f4
9 37 ms 25 ms 28 ms 10gigabitethernet13.switch4.ash1.he.net [2001:47
0:0:120::1]
10 58 ms 49 ms 49 ms 10ge6-3.core1.mci3.he.net [2001:470:0:30b::2]
11 63 ms 57 ms 65 ms 10ge5-1.core1.den1.he.net [2001:470:0:240::1]
12 103 ms 92 ms 98 ms 10ge13-5.core1.sjc2.he.net [2001:470:0:1b4::1]
13 85 ms 84 ms 93 ms 10ge1-2.core1.fmt2.he.net [2001:470:0:31::1]
14 89 ms 84 ms 83 ms www.buckeyeplanet.com [2001:470:1:12d:230:0:3:0]

Trace complete.

So in that case I'm seeing a little bit of slowdown between Denver and San Jose, but absolutely nothing of the sort that would cause any issues.

I'm fully over IPv6 (hence the odd looking IP addresses), but that shouldn't make any difference.
 
Upvote 0
None of this assumes it's on your end of course. Could well be that there's a problem switch somewhere, or someone (even he.net, though they're usually great about forewarning) is working on the network somewhere. Just wanted to give you the tools to try and sort out whether it's a local problem to you, something in between, or something at our facility in Freemont, CA.
 
Upvote 0
Cmd: unable to resolve target system name

Definitely sounds like a DNS issue. Those tend to resolve on their own, but I'll make sure our end is good. Are you having issues connecting to any other sites?

I switched my Windows boxes over to Google's DNS some time ago (away from Time Warner's). That may help, but you shouldn't have to go to that length.
 
Upvote 0
Upvote 0
Back
Top