Has anyone heard what the deal was last night on no ability to sync the Logos app nor access the website? It started here around 4:30-5:00 and lasted well after midnight.
I'm not going to complain to much...LOL "but" on a Wednesday night, OUCH!
I experienced the problem, too, but I'm not sure how to interpret what I saw. From my laptop in a Hyatt hotel, I could get to anywhere on the internet that I tried *except* any Logos-related site (community.logos.com, www.logos.com, biblia.com, and the sync domain). Best I can tell, the DNS infrastructure for Logos (Fibercloud ???) was having problems - the issue was that the DNS lookups for the Logos domains was timing out.
What made it more curious was that I could reach the Logos sites from my Blackberry. I thought that it might have just been something very weird with the hotel's connectivity (given that I could reach anyplace else). But if you had similar problems, it must have been a wider outage.
Donnie
I experienced the problem, too, but I'm not sure how to interpret what I saw. From my laptop in a Hyatt hotel, I could get to anywhere on the internet that I tried *except* any Logos-related site (community.logos.com, www.logos.com, biblia.com, and the sync domain). Best I can tell, the DNS infrastructure for Logos (Fibercloud ???) was having problems - the issue was that the DNS lookups for the Logos domains was timing out. What made it more curious was that I could reach the Logos sites from my Blackberry. I thought that it might have just been something very weird with the hotel's connectivity (given that I could reach anyplace else). But if you had similar problems, it must have been a wider outage. Donnie
Very interesting. So maybe some bad DNS records got propagated across more than just Fibercloud name servers yet not through the whole distributed NS system.
May be a few people upset on this one. Sparking another flare-up of "ANTI-CLOUD" computing.
In the words of colonel Klink, "I know nothing". But I understand your pain. :-)
I have nothing to truly complain about as our service wasn't halted. Truth is that most would agree that we have more issues on a semi frequent basis with a service being interrupted by “other” technical issues than cloud computing by itself would cause. Though the cloud would add one more variable to deal with.
LOL, "I know nothing". yes.... wait wasn't it Shultz who said that? [:D]
Looked to me like Fibercloud, a datacenter, went down, which would have taken Logos servers and DNS with it.
That's what I was thinking, right up until I could reach stuff from my Blackberry but not my laptop...
-Donnie
Kind of makes you wonder what a church would have had for its presentation software last night if they were using the new Logos version of "internet only" church presentation software.
This is why being "cloud-only" will be the reason I will not purchase some softwares. Here, with our internet service, we have several hours at a time where the internet in not available at all. And on a fairly frequent basis.
In the words of colonel Klink, "I know nothing".
That was Sargent Shultz (John Banner).
Recently watched the entire Hogan's Heroes series on DVD. Campy, but fun.
In the words of colonel Klink, "I know nothing". That was Sargent Shultz (John Banner). Recently watched the entire Hogan's Heroes series on DVD. Campy, but fun.
Apparently I really "know nuzzing" [:p]
In the words of colonel Klink, "I know nothing". That was Sargent Shultz (John Banner). Recently watched the entire Hogan's Heroes series on DVD. Campy, but fun. Apparently I really "know nuzzing"
Apparently I really "know nuzzing"
Maybe a nice, fresh [8] 'Shtrooooodle' [8] will help!
How come there was no official word on the event?
I second that request. If Logos is going to continue to go "cloud based" then all problems should be investigated and tracked so that users will have some history of problems and up-time data to know how much risk we may be of being out of service for items especially like the Proclaim software.
Here's the answer. (Summary: It wasn't us. :-) But we are now investigating ways to avoid this particular path and not be at risk here.)
Reason for Outage
Ticket:
Location: Bellingham
Service Impact: DNStraffic
Start: 5:45pm PT Date: 01/19/2011
End: 10:50pm PT Date: 01/19/2011
Duration:
Trouble Type: PartialDNS issue through one upstream provider
Trouble Resolution:
Overview:
The issue with DNSwas due to a path problem between one of our upstream providers and our DNSservers. This event was not a full outage. All traffic coming throughFiberCloud’s other upstream providers reached its destination without aproblem. Once FiberCloud rerouted traffic from the upstream provider thatwas having the path issue the problem was fixed.
FiberCloud will notroute traffic back through this provider until they have determined the causeand fixed the path issue.
I still have no sync
I appreciate your responding. I had no doubt you were on top of a solution but rather thought it odd that it wasn't mentioned.
I would add though that my durration was longer as there was no sync before 5:30pm CT and this outage included Logos.com domains and Bibla which were all offline till after 11:30pm CT.
I do understand that my longer durration may have more to do with me being further down the "DNS pipeline" and the potential time it takes for the correct record path to propagate through the NS system.
Thanks for the update.
Anthony
Anthony - your experience parallels mine
Mine too! The transatlantic pigeon got lost!
Bob,
Thank you very much for the response and its detail. Your honesty is refreshing in today's world.
God Bless and many continued years of business.
