Cloudflare One MASQUE Protocol Client Connectivity Issues Resolved

What happened

Cloudflare One experienced client connectivity issues affecting users of the MASQUE protocol starting May 1 at 22:06 UTC. The incident impacted enterprise customers using Cloudflare's Zero Trust platform for secure remote access. Cloudflare identified the root cause by 01:54 UTC on May 2 and implemented a fix by 02:38 UTC. The incident was fully resolved by 02:50 UTC on May 2, lasting approximately 4 hours and 44 minutes.

Business impact

Enterprise teams relying on Cloudflare One for remote workforce access faced potential connectivity disruptions during the outage window. Organizations using MASQUE protocol for secure tunneling may have experienced degraded or failed connections, potentially impacting remote worker productivity and secure application access.

Background

MASQUE is a newer HTTP-based protocol for secure proxying that Cloudflare One supports as part of its Zero Trust platform. The protocol enables secure connections through firewalls and NAT devices, making it valuable for enterprise remote access scenarios. Cloudflare One serves as a critical infrastructure component for many enterprise security architectures.

What this means for your team

Teams using Cloudflare One should verify that MASQUE protocol connections are functioning normally post-resolution and document any impact during the outage window. Consider implementing redundant connectivity methods or failover protocols for critical remote access scenarios. Review monitoring and alerting configurations to ensure rapid detection of Zero Trust platform issues that could affect remote workforce access.

What to watch

Monitor Cloudflare's status page for any follow-up communications about root cause analysis or preventive measures. Teams should watch for similar connectivity issues with MASQUE protocol implementations.

Sources

Cloudflare One client connectivity issues while using the MASQUE protocol
Cloudflare Status

Timeline

2d ago now