Localize incident
Partial Connectivity & Networking Disruption (Worker Service)
Localize experienced a minor incident on February 5, 2019 affecting Phrase Ingestion and Third-party Translation Ordering and 1 more component, lasting 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 05, 2019, 07:31 PM UTC
We are investigating a networking and connectivity problem causing increased latency and connectivity issues between a subset of our servers and other key infrastructure components. Currently this is affecting a small subset of servers which are responsible for performing background tasks affecting certain services noted below. Service status: Phrase Ingestion -- Degraded Performance. Our "overflow" system which is part of a redundancy system relating to phrase ingestion is experiencing an outage, however, the primary system responsible for phrase ingestion remains unaffected. The overflow system affected by this incident is not expected to affect Phrase Ingestion. In the unlikely event that this changes, the status of the Phrase Ingestion component will be updated. Translation ordering -- partial outage. Orders placed on the dashboard will not be immediately sent to the third-party translation provider. You may safely place new orders, and existing orders are unaffected. Newly placed orders will be received, but will experience a delay in the order's submission to the third-party translation provider pending resolution. Realtime translation deployment - partial outage. Real-time translation deployments are paused and queued to be performed when the Worker Service becomes fully operational. Changes to phrases and translations made during this incident will be deployed and will reflect on your live website when the incident is resolved. File Import / Export - degraded performance. File import and export may experience degraded performance.
- identified Feb 05, 2019, 07:53 PM UTC
The issue has been identified and a fix is being implemented.
- identified Feb 05, 2019, 07:56 PM UTC
The underlying issue has been resolved and the affected systems are being monitored to confirm resolution of the affected system components.
- monitoring Feb 05, 2019, 07:56 PM UTC
The underlying issue has been resolved and the affected systems are being monitored to confirm resolution of the affected system components.
- resolved Feb 05, 2019, 08:32 PM UTC
This incident and the underlying network connectivity issue has been resolved after switching to an alternate DNS provider.