Date: 3:01pm - 5:08pm ET January 11, 2021
Details: Starting 3:01 PM ET, a significant increase in query traffic caused our system to refuse connections. We added more processing resources to handle that additional load, which entered the herd at 4:04 PM ET and began to resolve the connection issue. The system is now fully operational.
Date: 2:24pm - 2:43pm ET August 25, 2020
Details: A brief certificate issue caused a small subset of image searches to be unavailable. The issue was resolved by a certificate re-issue, and Search.gov is now fully operational.
Date: 4:52pm - 5:15pm ET March 5, 2020
Details: At 4:52pm ET, Search.gov encountered an error due to an issue with data pulls for a migration. Service was restored once our clusters recovered at 5:15pm ET. Search.gov is now fully operational.
Date: 8:22am - 12:40pm ET March 6, 2020
Details: Search.gov saw a large number of errors on sites due to an issue originating on our application servers. The issue was resolved by a rolling restart of the environment and Search.gov is now fully operational.
Date: 7:02pm - 7:49pm ET March 5, 2020
Details: Beginning 7:02pm ET, an outage at our hosting provider prevented us from distributing incoming requests to our servers. Their issue was resolved, but in addition, a database update by them to an unused feature caused our internal requests to fail. We applied an update to match their update, and service was restored.
Date: 8:00 pm October 29 - 10:15 am October 30, 2019
Details: Beginning 8 PM ET 10/29, search sites using certain search features began returning errors for all searches. During our planned maintenance, our infrastructure host deployed routing settings to more servers than we requested, and this caused the error. After reverting the routing setting, all search sites are now behaving normally.
Date: August 31, 2019, 8:49am - 4:30pm ET
Details: An issue at our cloud hosting provider caused new logins to the Admin Center to fail. Searches were working normally.
Date: August 20, 2019, 9:30pm ET - August 21 9:50am ET
Details: An internal DNS issue caused our web index to return “No results” messages to some sites in their web results module. We have resolved the DNS issue and all systems are functioning normally.
Date: August 16, 2019, 10:30am - 3:30pm
Details: We performed unplanned maintenance to alleviate issues on search result pages and the Admin Center.
Date: August 12, 2019, 10:30am - 2:00pm, and from 2:30pm - 5:50pm ET
Details: We experienced two periods of intermittent errors and longer than usual load times, during high load to our results API. The load resulted in a reallocation process of our search indexes.
Date: July 17, 2019, 8am - approx 10:30am
Details: Server issues caused intermittent issues on search result pages (SERPs) and site Admin Centers.
Date: July 16, 2019, 10:30am-11:30am
Details: We conducted restarts of our servers to resolve memory issues. This resulted in intermittent degradation to search experiences.
Date: July 15, 2019, approx 1:51pm-6:15pm
Details: Memory issues in our back-end services caused intermittent issues when users attempted to complete searches.
Date: July 10, 2019, approx 2:35pm-2:50pm ET
Details: Deploy issues resulted in errors on search results pages (SERPs). We will address these issues before attempting future deploys.
Date: April 8, 2019, approx 8am-11:30am ET
Details: We experienced heavy load to our DNS, which we addressed through updating settings.
Date: March 11, 2019, 9:49am-1:55pm ET
Details: We experienced a transient issue with our back-end services which made some search data intermittently unavailable for the time indicated. No data was lost.
Date: January 30-31, 2019
Details: We experienced intermittent errors due to request queue volume. Errors resolved on retry. We performed maintenance on our primary index and increased the processing power for the machines that support this index.
||Systems are operating normally.
||Periodic errors that resolve themselves on retry.
||One or more components of the Search.gov service is unavailable, but other services are fully operational.
||The Search.gov service is down.