Status updates | PK Spot Incidents and maintenance reported on status page for PK Spot https://status.pkspot.app/ https://d1lppblt9t2x15.cloudfront.net/logos/3939459be5ebb52595ac0b11372eeded.png Status updates | PK Spot https://status.pkspot.app/ en Search outage with partial website degradation due to distributed scraping incident https://status.pkspot.app/incident/1108632 Thu, 29 Oct 2026 23:57:00 -0000 https://status.pkspot.app/incident/1108632#fdd7c8837a9f22e3a2ddcf48923e68db78a8434a0073cff8b219c93d011c3862 Incident On 30 October 2026, around 00:53–00:57 CET (29 October, 23:53–23:57 UTC), PK Spot experienced a search outage and degraded website performance during a distributed scraping incident. Some website requests continued to succeed; others were slow or failed. This is the identified incident window. The precise start and end of search unavailability are still being established. What happened Our edge logs show approximately 3,550 requests from 1,219 distinct IP addresses during the investigated window. Requests systematically traversed spot pages across all six supported languages, with additional requests to community and event pages. This pattern was consistent with sitemap enumeration. The traffic used rotating browser user-agent strings, including identities claiming older macOS, Windows, Android and iOS versions. Many requests also supplied a Google Search referrer. These headers did not establish that the requests came from Google; only a handful were identified as genuine Googlebot traffic. Most source addresses were in AWS-hosted ranges, including addresses beginning with 98.80., 54.91., 13.221., 18.207. and 44.221.. These are representative address prefixes, not attribution to an operator. We have not identified who conducted the scraping or established whether service disruption was their intention. Why it affected availability The scraping exposed a bug in our server-side rendering (SSR). When rendering map-related pages, a consent-handling subscription unintentionally triggered a download of the entire published community list from our search service—even though that data was not needed for the server-rendered page. Repeated page requests therefore generated excessive search traffic from our own backend. This overwhelmed the search cluster’s resources. As search requests stalled, the absence of an explicit application-level timeout left website renders waiting and occupied backend capacity. Incoming website requests were then delayed or rejected. The scraping was the trigger, but the amplification bug and insufficient timeout protection were weaknesses in our application. Impact - Search: unavailable during the incident. - Website: degraded performance and intermittent failures, rather than a complete outage. - Backend: capacity exhaustion produced 1,069 HTTP 429 responses and 16 HTTP 503 responses in the investigated request window. - Performance: some rendering requests took tens of seconds, with recorded latency reaching approximately 79 seconds. Current status and remediation Service has recovered, and we are currently fixing the SSR bug. A fix has been prepared but is not yet being presented as deployed and verified. Our immediate priorities are to prevent unnecessary community-list downloads during server rendering, add bounded search-request timeouts with graceful failure handling, and verify that concurrent page requests cannot recreate this amplification. We are also reviewing protections against excessive automated traffic. Those protections complement—not replace—fixing the application behavior that made this incident possible. We’re sorry for the disruption. We will update this report once the fix has been deployed and validated. https://github.com/lukasbuehler/pkspot/pull/129 Search outage with partial website degradation due to distributed scraping incident https://status.pkspot.app/incident/1108632 Thu, 29 Oct 2026 23:53:00 -0000 https://status.pkspot.app/incident/1108632#af332b926c3c485580a9539ec024a8fb4b81c6f916d9407626f173bd67adf164 Incident Start of the scraping incident was around 00:51 CET. The issue was first detected around 00:53 CET when our search was timing out. Intermittent profile loading failures https://status.pkspot.app/incident/1100256 Thu, 22 Oct 2026 22:49:00 -0000 https://status.pkspot.app/incident/1100256#2ee703551f804a7dfbd2813e3c3441d4305d449c3d2256074150f9b495df42c3 Incident Profile requests were succeeding again by 00:49 CEST. The incident is resolved. The exact recovery time and underlying cause remain unconfirmed. Intermittent profile loading failures https://status.pkspot.app/incident/1100256 Thu, 22 Oct 2026 22:42:00 -0000 https://status.pkspot.app/incident/1100256#61044e8177719a1d0b53068eabf3286e46d8e29aa4690f68440998c869bac3e8 Incident Some user profiles temporarily failed to load. Monitoring recorded 16 server errors between approximately 00:42 and 00:44 CEST on 23 October 2026. Successful profile requests were observed again by 00:49 CEST. The underlying cause has not been confirmed. This report was added retrospectively.