Update at midnight GMT
We are pleased to announce that the situation continues to improve. The sign-on problems have been resolved. Skype presence and chat may still take a few more hours to be fully operational. We know what our faithful users have been going through and we thank you for your patience and kind support.
Context & Ripple Effects
Two days after Skype first flagged login problems on August 16, the company's Heartbeat status channel is reporting measurable recovery rather than another escalation — this midnight GMT note follows the recovery announcement on Skype Blogs the same day.
The significance of the update is narrow but real: sign-on is back, which means users can authenticate again, while presence and chat lag behind. For a service whose entire proposition is being reachable, the distinction between restored sign-on and fully operational presence is what determines whether the outage is over for any individual user.
First-order effects
- Skype users regain the ability to sign in immediately, but presence indicators and chat sessions remain degraded for hours longer, so contacts cannot yet rely on seeing accurate availability status.
- Skype's Heartbeat page becomes the sole authoritative source of recovery progress, concentrating user attention on a single status channel during the tail end of the incident.
Second-order effects
- Every hour that presence stays inaccurate after sign-on returns extends the period where businesses and heavy callers using Skype for coordination face unreliable contactability — the practical cost of the outage persists past the headline fix.
- A multi-day authentication outage on a free-but-embedded communications tool pushes dependent users to keep fallback channels open, a behavioral shift competitors in consumer VoIP can court directly.
Third-order effects
- If a peer-to-rooted sign-on architecture can fail globally for days, the episode strengthens the case that consumer VoIP reliability becomes a procurement criterion, not just a feature comparison — and that vendors owe continuous public status disclosure as standard practice.
The trend: Consumer VoIP is maturing into critical contact infrastructure, where a single vendor's authentication outage is no longer a private glitch but a widely felt availability event that demands public, running status updates.