1E Outage History

A subset of 1E users experienced technical issues with managed devices visibility, causing degraded performance for approximately 1.6 hours. The engineering team identified and fixed the underlying issue that caused the performance problems. The incident was resolved after a monitoring period to ensure the system had stabilized.

A subset of clients experienced connectivity issues when accessing 1E's DEX services in the UK South 1 region for 1.5 hours. The issue affected both switches and DEX client connections, preventing users from properly accessing the service. Engineers identified the root cause and applied a fix to restore client connections, with the incident fully resolved after monitoring confirmed system stability.

The 1E service experienced a major incident where managed devices were missing from the device list. This issue affected device visibility and management capabilities for users. The problem was resolved after 1.1 hours when a fix was implemented and monitoring confirmed the restoration of normal service.

The 1E service experienced a major incident where the managed device list failed to display properly. This issue prevented users from viewing their managed devices for 54 minutes. The problem was resolved after implementing a fix and monitoring the results.

A subset of 1E users experienced license validation pop-ups in TeamViewer that prevented normal usage of the service. The issue was resolved after 44 minutes by fixing the license validation system, with users needing to restart the TeamViewer service to clear the pop-up messages. All systems returned to full functionality following the fix.

The 1E service experienced high load on TeamViewer Services, causing a major service incident that lasted 44 minutes. A fix was implemented and monitored to ensure stability. The incident was fully resolved after confirming no further issues occurred.

The 1E DEX service experienced client connectivity issues with the West Europe 1 switch infrastructure, causing client disconnections over a 3.3-hour period. Affected clients were able to reconnect automatically during the incident. The issue was resolved after implementing a fix and monitoring the results.