Looks like it. It was 404-ing earlier, but it was definitely an issue on their end (since it was a site-specific 404 page).