Time: Oct. 6, 2022, 3:24 p.m.

Status: Resolved

Update: Error rates have ceased (for over 10 minutes) and we're marking this as resolved.

Time: Oct. 6, 2022, 3:15 p.m.

Status: Monitoring

Update: We are observing a region-specific incident on the "edge" nodes in Lisbon, Portugal that are responsible for serving Skedda requests in that broad geographic area. The incident is isolated to traffic passing through this edge node, i.e. isolated to customers that are closer to the Lisbon edge node than any other edge node. This incident is likely responsible for any elevated latency or error rates that may be experienced by customers in this area of Europe. Customers in other regions of the world should not be affected by this incident. The root cause appears to be related to the state of the edge servers in this region. We are monitoring Microsoft's resolution efforts for this incident (it's related to Azure Front Door, which Skedda uses for this service) and will provide an update within 60 minutes or as events warrant.

Time: Sept. 7, 2022, 8:32 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: Sept. 7, 2022, 7:55 p.m.

Status: Monitoring

Update: Although we are observing normal performance on our side, we are continuing to monitor Azure's status page for confirmation that residual impact has been resolved (https://status.azure.com/en-us/status). We will provide another update at that time.

Time: Sept. 7, 2022, 6:15 p.m.

Status: Monitoring

Update: We are observing normal performance levels again since we implemented the mitigation step. We are continuing to monitor and will provide another update within 60 minutes or as events warrant.

Time: Sept. 7, 2022, 5:36 p.m.

Status: Monitoring

Update: We have implemented a network mitigation step from our side in order to reduce the effects of the Azure Front Door incident. We are seeing signs of recovery for a significant portion of traffic. We are continuing to monitor and will provide an update within 30 minutes or as events warrant.

Time: Sept. 7, 2022, 5:06 p.m.

Status: Monitoring

Update: Microsoft has confirmed the incident on its status page: https://status.azure.com/en-us/status Considering the magnitude of this incident for Microsoft's services generally (Azure Front Door is used by many Microsoft services), we anticipate that Microsoft will resolve the issue promptly and we are continuing to monitor their efforts. We will provide an update within 30 minutes or as events warrant.

Time: Sept. 7, 2022, 4:58 p.m.

Status: Identified

Update: We have isolated the cause of the issue to Skedda's Web-Application Firewall layer, which consists of a global network of edge nodes for performance and traffic management. The service that Skedda uses for this layer, Azure Front Door, is currently experiencing intermittent connectivity and performance issues when forwarding requests to our back-end servers. Retrying requests may succeed, and some regions/geographies may be less effected than others. We are continuing to work on a resolution for this issue and will provide an update within 30 minutes or as events warrant.

Time: Sept. 7, 2022, 4:41 p.m.

Status: Investigating

Update: We are currently investigating intermittently elevated latency and errors on our web and mobile applications. We will provide an update within 20 minutes or as events warrant.

Time: Sept. 7, 2022, 8:32 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: Sept. 7, 2022, 7:55 p.m.

Status: Monitoring

Update: Although we are observing normal performance on our side, we are continuing to monitor Azure's status page for confirmation that residual impact has been resolved (https://status.azure.com/en-us/status). We will provide another update at that time.

Time: Sept. 7, 2022, 6:15 p.m.

Status: Monitoring

Update: We are observing normal performance levels again since we implemented the mitigation step. We are continuing to monitor and will provide another update within 60 minutes or as events warrant.

Time: Sept. 7, 2022, 5:36 p.m.

Status: Monitoring

Update: We have implemented a network mitigation step from our side in order to reduce the effects of the Azure Front Door incident. We are seeing signs of recovery for a significant portion of traffic. We are continuing to monitor and will provide an update within 30 minutes or as events warrant.

Time: Sept. 7, 2022, 5:06 p.m.

Status: Monitoring

Update: Microsoft has confirmed the incident on its status page: https://status.azure.com/en-us/status Considering the magnitude of this incident for Microsoft's services generally (Azure Front Door is used by many Microsoft services), we anticipate that Microsoft will resolve the issue promptly and we are continuing to monitor their efforts. We will provide an update within 30 minutes or as events warrant.

Time: Sept. 7, 2022, 4:58 p.m.

Status: Identified

Update: We have isolated the cause of the issue to Skedda's Web-Application Firewall layer, which consists of a global network of edge nodes for performance and traffic management. The service that Skedda uses for this layer, Azure Front Door, is currently experiencing intermittent connectivity and performance issues when forwarding requests to our back-end servers. Retrying requests may succeed, and some regions/geographies may be less effected than others. We are continuing to work on a resolution for this issue and will provide an update within 30 minutes or as events warrant.

Time: Sept. 7, 2022, 4:41 p.m.

Status: Investigating

Update: We are currently investigating intermittently elevated latency and errors on our web and mobile applications. We will provide an update within 20 minutes or as events warrant.

Time: July 21, 2022, 12:30 p.m.

Status: Resolved

Update: Zapier has resolved the cause of the errors and this is now resolved.

Time: July 21, 2022, 9:04 a.m.

Status: Identified

Update: Zapier's trigger-receiving endpoints are currently intermittently failing with server errors (on Zapier's side). This means that a subset of the triggers (e.g. triggers to start a "New user booking" flow in Zapier) that Skedda sends to Zapier are not being successfully received by Zapier. Skedda has automatic retry logic in place, so triggers will typically succeed on a subsequent retry (retries are attempted at 15-minute intervals). This incident is only relevant to those customers that use Zapier with Skedda. We are monitoring Zapier's efforts to resolve this incident and will provide an update within 2 hours or as events warrant.

Time: July 21, 2022, 12:30 p.m.

Status: Resolved

Update: Zapier has resolved the cause of the errors and this is now resolved.

Time: July 21, 2022, 9:04 a.m.

Status: Identified

Update: Zapier's trigger-receiving endpoints are currently intermittently failing with server errors (on Zapier's side). This means that a subset of the triggers (e.g. triggers to start a "New user booking" flow in Zapier) that Skedda sends to Zapier are not being successfully received by Zapier. Skedda has automatic retry logic in place, so triggers will typically succeed on a subsequent retry (retries are attempted at 15-minute intervals). This incident is only relevant to those customers that use Zapier with Skedda. We are monitoring Zapier's efforts to resolve this incident and will provide an update within 2 hours or as events warrant.