Guys, we really need an update on this. I understand if you don;t
have a resolution, but not responding at all is not cool. Looks like
maybe Tweetsharp, the API we use, thinks the problem is resolved, but
our customers are still DOWN. Do we need to redeploy a workaround?
What is the ETA?
On
Sorry, missed your last reply. Anyway, we are still down. I assume
propagation *should* have happened - what can we do to debug this?
On May 7, 10:39 am, melissa melissaleff...@gmail.com wrote:
Guys, we really need an update on this. I understand if you don;t
have a resolution
something.
Thanks so much for replying. BTW, check out our app sometime, it's
pretty cool ;).
Melissa, Awareness Inc.
On May 7, 12:03 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Melissa,
We had to pause the cache expiration for a little while yesterday afternoon,
but it resumed
Taylor, one of our users is now working, I guess we are on the last
servers.not sure if there is any timeframe we can tell our
customers hen we know this will be completed.
Thanks, Melissa
www.awarenessnetworks.com
Follow us on Twitter http://twitter.com/awarenessinc
On May 7, 12:03 pm
Any ETA? We need to know how long, and propagation time, or we will
have to deploy a workaround. It's been about 24 hours now, and t is
affecting our customers.
Thanks, Melissa, Awareness
On May 6, 12:19 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
We're working on getting
