USCCB site down?

  • Thread starter Thread starter indiecath
  • Start date Start date
Status
Not open for further replies.
I

indiecath

Guest
Does anyone know whats going on with USCCB web page? Its like its been watered down with ads and downloads for the comp and its orange and not green. I cant get to the daily readings or anything else for that matter.
 
That is an automatically generated page that comes up when a domain is not associated with that web address. Normally, a notification is made if maintenance is in progress on an established domain. Since the Vatican site has recently been hacked, there is also a possibility that the USCCB site has been hacked. We will see.
 
I’ve noticed this as well. It happens when I attempt to access the USCCB domain from my Amazon Kindle Fire. Instad of the official USCCB webpage, it’s a placeholder page by a web domain company. This causes problems with the Laudate app, which downloads the daily lectionary readings from the USCCB website. The issue does not seem to occur on my laptop.
 
=indiecath;9094487]Does anyone know whats going on with USCCB web page? Its like its been watered down with ads and downloads for the comp and its orange and not green. I cant get to the daily readings or anything else for that matter.
Click to expand...
usccb.org/

I just tried it and it working FINE:D
 
This is happening to me right now, 24 March, 8:30AM Central Europe time. Same as yesterday evening. It happens to me about 75% of the time I want to open the USCCB site. I keep getting sent in a circle.

First I go to my favorites and click on USCCB. Then I get a message saying ‘Ooops, Internet Explorer has not found USCCB org.’ I can try accessing a copy of the page or searching on Google. If I try accessing a copy of the page, I get a grey box that tells me it is a copy of the page, but the page is blank.

Next I’m back at the ‘Ooops’ message. When I try searching Google, it gives me Google search results and when I click on the USCCB link, the whole circle starts again.

I tried searching in Google Chrome and the same thing happened. Maybe I’ll download Firefox to see if it’s somehow my computer or my search engine.

Once when I had this problem, a few hours later I was in my parish and we had no problem accessing USCCB from the parish office. When I went home, it was fine at home, too.

By the way, sometimes I get the same thing with Catholic Answers, but it doesn’t go in a circle. After the ‘Oops’ message, I can get to Catholic Answers.

I can’t remember if I’m having the problem with other sites or only other Catholic sites. I haven’t been keeping a record, though I know that with USCCB, I never know whether I’ll get access to it or not.
 
Contact your Internet Provider and inform them that you are having DNS problems. DNS (Domain Name System) is like the “white pages” of the Internet. It is the system that translates names (www.usccb.org) into IP address numbers (69.63.132.76). If DNS malfunctions then you may have problems reaching some sites or all sites. Experts can get around DNS errors by saving the IP addresses beforehand and using them instead of the names, but 99% of users out there rely on DNS every time they connect to an Internet site.

It is possible to change your DNS servers if they are producing errors. There are free DNS services on the Internet, some may be open for anyone to use, while some may require that you send an email request for access. These services may be more reliable but slower than your ISP’s own servers. Your ISP may have multiple DNS servers that you can try in a different order before trying another service.

I run my own caching-only DNS server on my Ubuntu Linux system. 99% of users out there rely on one or more remote DNS servers.

I am fairly confident that your errors are DNS-related. Others encountering these errors should check that they did not make a typo in the name. Going to uscb.org by mistake, for example, will land you on a “parked domain” website with no useful links and just ads. But if you follow a site from your favorites or bookmarks, there can be no typo and it points to DNS errors.
 
It’s March 27 and we cannot access the usccb website either. We get a website search page from our phone company… hard to believe its DNS related, but I’ll check that out as well.
 
March 29th. I’m having same problem and its happend before, even on different computer and network. Its them. Don’t know what the trouble is, but I take it as a good sign (though I’m grumbling in frustration because I have an rss feed from them on my website). So many people are keeping up with Catholic news that their sit is going down!. At least I hope that’s the explanation!
 
Status
Not open for further replies.
Back
Top