Abstract: Technologies are disclosed for shortening and/or minimizing service interruptions. An incident service executing within a service provider network is used to detect an incident that has caused a service interruption and performs operations to assist in resolving the service interruption. The incident service may identify resources (e.g., computing resources, individuals, . . . ) to triage and remediate the service interruption. For instance, the incident service may provide information to one or more users of a customer experiencing a service interruption to assist in guiding the user(s) to address one or more problems to assist in resolving the service interruption. The information may include information such as providing one or more recommendations to configure one or more services, such as one or more actions to perform (e.g., a step-by-step runbook).

Abstract: An origin server that is implemented within one or more devices within a third party virtual private cloud (VPC) is provided herein. Instead of communicating with various CDNs over a public network, the third party VPC may instead communicate with a managed VPC via a private network. Thus, no gateway, network address translation (NAT), or other such devices may be needed for the third party VPC and the managed VPC to communicate. Rather, a VPC identifier of the managed VPC and a VPC identifier of the third party VPC are used to pair the two VPCs. Once paired, a private route is set up such that points from the private address space of the third party VPC to the private address space of the managed VPC. The managed VPC then communicates directly with the various CDNs via a public network.

Abstract: The present disclosure generally relates to a failover management service that can continuously monitor attributes of regional network resources to characterize resource availability per region. The failover management service associates the regional resource availability information with a set of hash values in which each individual hash value is representative a concatenation of a resource identifier and a client identifier associated with one or more individual clients. For individual hash values, the failover management service associates failover information, which is propagated to a DNS service. If a network-resource becomes unavailable, clients can transmit DNS queries including a hash value that discovers the appropriate failover information for the specific network-based resource and client device.

Abstract: An origin server that is implemented within one or more devices within a third party virtual private cloud (VPC) is provided herein. Instead of communicating with various CDNs over a public network, the third party VPC may instead communicate with a managed VPC via a private network. Thus, no gateway, network address translation (NAT), or other such devices may be needed for the third party VPC and the managed VPC to communicate. Rather, a VPC identifier of the managed VPC and a VPC identifier of the third party VPC are used to pair the two VPCs. Once paired, a private route is set up such that points from the private address space of the third party VPC to the private address space of the managed VPC. The managed VPC then communicates directly with the various CDNs via a public network.

Abstract: An origin server that is implemented within one or more devices within a third party virtual private cloud (VPC) is provided herein. Instead of communicating with various CDNs over a public network, the third party VPC may instead communicate with a managed VPC via a private network. Thus, no gateway, network address translation (NAT), or other such devices may be needed for the third party VPC and the managed VPC to communicate. Rather, a VPC identifier of the managed VPC and a VPC identifier of the third party VPC are used to pair the two VPCs. Once paired, a private route is set up such that points from the private address space of the third party VPC to the private address space of the managed VPC. The managed VPC then communicates directly with the various CDNs via a public network.

Abstract: Methods, systems, and computer-readable media for real-time estimation of working sets are disclosed. A plurality of counters are initialized. The counters represent cardinality estimates of data elements accessed for respective time intervals. A request for data is received during the respective time intervals. One or more data elements are determined that are accessed in responding to the request. The counters are updated using the one or more data elements, such that one of the counters is increased by a quantity of the data elements that are accessed for the first time during the respective time interval. The working set estimates for the respective time intervals are determined using the counters.

Abstract: Each point-of-presence advertises the network addresses it hosts and the network addresses hosted by other points-of-presence. Each point-of-presence also announces its own network addresses at a higher degree of specificity than the other network addresses it is announcing. When a point-of-presence fails, packets routed to a network address hosted by that point-of-presence will be routed to one of the other points-of-presence announcing the same network address. When a point-of-presence is available, its more specific network address announcements prevents packets routed to a network address hosted by that point-of-presence from being routed to any other point-of-presence.

Abstract: The following description is directed to storing properties of requests to potentially block future requests having similar properties. In one example, a request can be received. A property of the request can be stored so that the property persists across an initialization sequence of a computer system. At least the property can be used to determine whether to block any future requests having similar properties.