tag:status.nimbleway.com,2005:/history Nimble Status - Incident history 2026-05-10T04:30:00.000+00:00 Nimble tag:status.nimbleway.com,2005:Incident/cmozkn5ki0dmtoe8tvpta5b4w 2026-05-10T04:30:00.000+00:00 2026-05-10T04:30:00.000+00:00 Web APIs Errors - All vx6, some vx8 and vx10. All async Type: Incident

Duration: 5 hours and 54 minutes

Affected Components: Nimble Data API

May 10, 04:30:00 GMT+0
Investigating - We are experiencing system errors in some services, the team is looking into it..

May 10, 10:24:20 GMT+0
Resolved - This incident has been **resolved** \- Between **04:00–06:00 UTC** the API experienced degraded availability. Partial impact continued until **07:30 UTC**, after which all systems returned to normal operation..

]]> tag:status.nimbleway.com,2005:Incident/cmotuugfj00vu11jhp6ykuisz 2026-05-06T08:00:05.165+00:00 2026-05-06T08:00:05.165+00:00 Service degradation - Mostly Async requests, some WSA and realtime web api requests Type: Incident

Duration: 1 hour and 30 minutes

Affected Components: Nimble Data API

May 6, 08:00:05 GMT+0
Investigating - We are currently investigating this incident..

May 6, 08:57:05 GMT+0
Investigating - We are currently investigating this incident..

May 6, 09:29:45 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.nimbleway.com,2005:Incident/cmoi1cbd30b94x6zdid34cw54 2026-04-28T00:00:00.000+00:00 2026-04-28T00:00:00.000+00:00 Service issue - web API (vx6, vx8, vx10) and proxy Type: Incident

Duration: 3 hours and 42 minutes

Affected Components: Nimble IP, Nimble Data API

Apr 28, 00:00:00 GMT+0
Investigating - We are currently investigating this incident..

Apr 28, 02:25:04 GMT+0
Investigating - We are currently investigating this incident..

Apr 28, 03:41:39 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.nimbleway.com,2005:Incident/cmohdf01i1ekpfjehskcnbqaq 2026-04-27T15:05:00.000+00:00 2026-04-27T15:05:00.000+00:00 Degraded performance with VX8 and VX10 drivers Type: Incident

Duration: 1 hour and 16 minutes

Affected Components: Nimble Browser

Apr 27, 15:05:00 GMT+0
Investigating - We've identified an issue with our VX8 and VX10 drivers. All other drivers are working as expected..

Apr 27, 16:20:56 GMT+0
Resolved - This incident has been resolved. All drivers are now back to full operational capacity..

]]> tag:status.nimbleway.com,2005:Incident/cmm3bxn8600019pgcomlx7qs3 2026-02-26T10:37:45.202+00:00 2026-02-26T10:37:45.202+00:00 Web search agents temporarily not available Type: Incident

Duration: 33 minutes

Affected Components: Nimble Data API

Feb 26, 10:37:45 GMT+0
Investigating - We are currently investigating this incident..

Feb 26, 11:11:04 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.nimbleway.com,2005:Incident/cmkh0kgx1068h2zbue1qcdmmf 2026-01-16T03:50:00.000+00:00 2026-01-16T03:50:00.000+00:00 High Error Rates Type: Incident

Duration: 5 hours and 40 minutes

Affected Components: Nimble IP

Jan 16, 03:50:00 GMT+0
Investigating - Higher error rates (\~16% at the peak, \~8% on average) occurred between 10:50 PM on Jan 15 and 12:23 AM on Jan 16 (EST) due to a sync issue..

Jan 16, 09:30:00 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.nimbleway.com,2005:Incident/cmk76bojc0ajg87lsla4jswsf 2026-01-06T17:30:00.000+00:00 2026-01-06T17:30:00.000+00:00 Incident Impact: Connection error and disconnections with Proxies Type: Incident

Duration: 17 hours and 30 minutes

Affected Components: Nimble IP

Jan 6, 17:30:00 GMT+0
Identified - We are continuing to work on a fix for this incident..

Jan 7, 11:00:00 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.nimbleway.com,2005:Incident/cmh1ovc1l008j147sdaom5jt1 2025-10-22T07:45:48.338+00:00 2025-10-22T07:45:48.338+00:00 Web API service issue Type: Incident

Duration: 37 minutes

Affected Components: Nimble Data API

Oct 22, 07:45:48 GMT+0
Investigating - We are currently investigating this incident..

Oct 22, 08:23:10 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.nimbleway.com,2005:Incident/cmgkp89bq0129yuud3ul7mxgf 2025-10-10T06:40:00.000+00:00 2025-10-10T06:40:00.000+00:00 Web API issues Type: Incident

Duration: 1 hour and 20 minutes

Affected Components: Nimble Data API

Oct 10, 06:40:00 GMT+0
Identified - We are working on an incident..

Oct 10, 08:00:00 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.nimbleway.com,2005:Incident/cmcxbl97i001vvnbnyitli70j 2025-07-10T11:44:08.839+00:00 2025-07-10T11:44:08.839+00:00 Service Errors Type: Incident

Duration: 1 hour and 7 minutes

Affected Components: Nimble Data API

Jul 10, 11:44:08 GMT+0
Investigating - We are experiencing system errors Web API service, the team is looking into it..

Jul 10, 12:16:20 GMT+0
Identified - We are continuing to work on a fix for this incident..

Jul 10, 12:51:14 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.nimbleway.com,2005:Incident/cm91n9gbr0001s4s105cn555a 2025-04-03T10:30:00.000+00:00 2025-04-03T10:30:00.000+00:00 Service Errors Type: Incident

Duration: 19 hours and 31 minutes

Affected Components: Nimble Data API

Apr 3, 10:30:00 GMT+0
Identified - We are experiencing system errors in some services, the team is looking into it..

Apr 3, 21:40:00 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.nimbleway.com,2005:Incident/cm6z6zrge0003sfngyujsq6ng 2025-02-10T15:12:45.699+00:00 2025-02-10T15:33:32.468+00:00 Web API - render=false, some requests fail Type: Incident

Duration: 21 minutes

Affected Components: Nimble Data API

Feb 10, 15:33:32 GMT+0
Resolved - This incident has been resolved..

Feb 10, 15:12:45 GMT+0
Investigating - We are currently investigating this incident..

]]> tag:status.nimbleway.com,2005:Incident/cm6knlx7n000f13ozfbo8y8ho 2025-01-31T11:01:21.010+00:00 2025-01-31T11:01:21.010+00:00 Service issues - Web API Type: Incident

Affected Components: Nimble Data API

Jan 31, 11:01:21 GMT+0
Resolved - This incident has been resolved. Impact was 10:20 UTC - 11:15 UTC.

]]> tag:status.nimbleway.com,2005:Incident/cm66mkotl001zd4xxly2lk2ib 2025-01-15T08:00:00.000+00:00 2025-01-19T08:00:00.000+00:00 Google SERP Incident - RCA Type: Incident

Duration: 28 days

Affected Components: Nimble Data API

Jan 19, 08:00:00 GMT+0
Resolved - Fix deployed, we are monitoring the results..

Jan 15, 08:00:00 GMT+0
Identified - ### **The Change (January 15th)** On January 15th, Google introduced a significant update to their website, requiring JavaScript execution to retrieve search results. Traditionally, the Search Engine Results Page (SERP) industry relied on HTTP requests to Google, such as `curl` requests, simulating browser behavior by including headers like `User-Agent`, `Client-Hints`, etc. Previously, requests could even be made without cookies, effectively replicating an incognito browser search. With the new update, Google now serves a page containing a script (possibly accompanied by an anti-bot challenge) that redirects to the actual search results page with an additional dynamically generated query parameter, `sei`. However, directly accessing the URL with the `sei` parameter is not feasible due to the absence of proper cookies, leading to a block or CAPTCHA (the infamous "Sorry" page). Solving the CAPTCHA is technically possible but highly inefficient and costly compared to traditional SERP requests. Moreover, even accessing the `/search` URL from the homepage results in the redirect page unless proper cookies are set. The only way to acquire these cookies is to execute a search, render the JavaScript, bypass the redirect, and reach the search results page. Notably, Google has added multiple new cookies to facilitate this process. ### **The Old Methods** Historically, Google search results were obtained using two approaches: * **Without Cookies:** Typically used for enhancing ads since Google tended to serve more ads to requests without cookies. * **With Cookies:** Used in cases where ads were not the primary focus. Both methods utilized the `vx6` driver for efficient and lightweight interactions. ### **The Mitigation (January 16th–18th)** As the update rolled out, block rates began to rise, and the number of empty Google HTML responses increased significantly. To address this, we transitioned Google SERP requests to the `vx8` driver. This involved rendering the JavaScript, waiting for the actual search results page to load, and retrieving the data. While this ensured valid SERP requests, it came at a cost: * Response times increased from \~2–4 seconds to 10 seconds or more. * The system's ability to scale during traffic spikes was reduced, as creating and managing multiple browser instances required substantial resources. ### **The Solution (January 19th)** ### To maintain an efficient and competitive SERP API, we developed a custom cookie generation flow. This process involved performing a preliminary search for a random term, saving the resulting cookies, and using them for subsequent requests. After deploying this solution, additional adjustments were made to address: * **Mobile SERP:** Mobile search pages differ significantly from desktop versions. * **GDPR Compliance:** Handling variations when requests originated from Europe. Following these fixes, the SERP API regained its original speed and accuracy. ### **Ads Optimization** The ads optimization feature, which previously relied on cookie-less `curl` requests, is no longer viable under the new changes. While further research is required to adapt to Google's updated ad policies, the feature has been transitioned to the `vx8` driver. Although this approach is slower and more resource-intensive, it remains functional and appears to yield more ads in response. Ongoing monitoring and adjustments will be necessary to optimize ad-related processes under the new system..

]]> tag:status.nimbleway.com,2005:Incident/cm5pcmux7006rdi8kqia4umg8 2025-01-09T13:13:17.216+00:00 2025-01-09T15:34:53.375+00:00 Authentication issue - login across products not available. Web API activity not available. Type: Incident

Duration: 2 hours and 22 minutes

Affected Components: Nimble Data API

Jan 9, 15:34:53 GMT+0
Resolved - This incident has been resolved..

Jan 9, 13:13:17 GMT+0
Investigating - We are currently investigating this incident..

]]> tag:status.nimbleway.com,2005:Incident/cm4veal9z00237x1mcazyrmdz 2024-12-19T14:06:39.326+00:00 2024-12-19T15:04:25.299+00:00 Service not available Type: Incident

Duration: 2 days, 9 hours and 46 minutes

Affected Components: Nimble Data API

Dec 19, 15:04:25 GMT+0
Resolved - This incident has been resolved..

Dec 19, 14:06:39 GMT+0
Investigating - We are currently investigating this incident..

]]> tag:status.nimbleway.com,2005:Incident/cm4tnik9t000r10lpqirncdqn 2024-12-18T08:49:15.395+00:00 2024-12-18T14:07:46.477+00:00 Degraded service - some customers Type: Incident

Duration: 7 hours and 12 minutes

Affected Components: Nimble Data API

Dec 18, 14:07:46 GMT+0
Monitoring - Fix deployed, monitoring.

Dec 18, 08:49:15 GMT+0
Investigating - We are currently investigating this incident..

Dec 18, 10:11:31 GMT+0
Identified - We are continuing to work on a fix for this incident..

Dec 18, 16:01:22 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.nimbleway.com,2005:Incident/cm4b27a2w001x89xa3vl0ix70 2024-12-05T08:32:45.883+00:00 2024-12-05T08:32:45.883+00:00 Proxy issues - service degradation Type: Incident

Duration: 2 hours and 52 minutes

Affected Components: Nimble IP

Dec 5, 08:32:45 GMT+0
Investigating - We are currently investigating this incident..

Dec 5, 11:24:43 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.nimbleway.com,2005:Incident/cm49vc946008h5ujkkldgt5dw 2024-12-04T12:32:54.392+00:00 2024-12-04T12:32:54.392+00:00 Service Degradation - Some Customers Type: Incident

Duration: 1 hour and 9 minutes

Affected Components: Nimble Data API

Dec 4, 12:32:54 GMT+0
Investigating - We are currently investigating this incident..

Dec 4, 13:15:34 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Dec 4, 13:42:10 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.nimbleway.com,2005:Incident/cm3wu9kxy001dz46med1fsl2b 2024-11-25T09:41:49.802+00:00 2024-11-25T09:41:49.802+00:00 Service Degradation - some customers Type: Incident

Duration: 6 hours and 54 minutes

Affected Components: Nimble Data API

Nov 25, 09:41:49 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Nov 25, 16:35:23 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.nimbleway.com,2005:Incident/cm13hlukj00293omlvts1g4ym 2024-09-15T06:30:00.000+00:00 2024-09-15T08:05:00.000+00:00 Service Errors in Nimble IP Type: Incident

Duration: 1 hour and 35 minutes

Affected Components: Nimble IP, Nimble Dashboard

Sep 15, 08:05:00 GMT+0
Resolved - This incident has been resolved..

Sep 15, 06:30:00 GMT+0
Investigating - We are experiencing some high error rates in Nimble IP service, the team is looking into it..

Sep 15, 07:00:00 GMT+0
Identified - The root cause has been found. .

]]> tag:status.nimbleway.com,2005:Incident/cm05azp4j002d6y52wnas82oi 2024-08-22T09:00:00.000+00:00 2024-08-22T13:20:00.000+00:00 Service Errors Type: Incident

Duration: 4 hours and 20 minutes

Affected Components: Nimble IP

Aug 22, 13:20:00 GMT+0
Resolved - This incident has been resolved..

Aug 22, 09:00:00 GMT+0
Investigating - We are experiencing system errors in Nimble Proxies, the team is looking into it..

Aug 22, 12:48:00 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

]]> tag:status.nimbleway.com,2005:Incident/clyeeo0ao72566h5oizy0l5bp1 2024-07-09T09:25:00.000+00:00 2024-07-09T09:25:00.000+00:00 Service Errors Type: Incident

Duration: 1 hour and 5 minutes

Affected Components: Nimble Data API

Jul 9, 09:25:00 GMT+0
Investigating - We are experiencing system errors in Web API, the team is looking into it..

Jul 9, 10:30:00 GMT+0
Resolved - We experienced unexpected error in one of our servers, this was resolved and we are taking the necessary actions to avoid reoccurrence . .

]]> tag:status.nimbleway.com,2005:Incident/cly33ycgi14404blmzfeijg0pu 2024-06-30T14:52:00.000+00:00 2024-06-30T15:10:00.000+00:00 Service Errors - Render Type: Incident

Duration: 18 minutes

Affected Components: Nimble Data API

Jun 30, 15:10:00 GMT+0
Resolved - This incident has been resolved..

Jun 30, 14:52:00 GMT+0
Identified - We are experiencing system errors in some render: true requests , the team is looking into it..

]]> tag:status.nimbleway.com,2005:Incident/clxfz3vo461103bglttpz1ioof 2024-06-15T07:00:00.000+00:00 2024-06-15T07:00:00.000+00:00 Service outage Type: Incident

Duration: 4 hours

Affected Components: Nimble Browser, Nimble Data API

Jun 15, 07:00:00 GMT+0
Investigating - We are experiencing some outages in Nimble service, the team is looking into it..

Jun 15, 10:00:00 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Jun 15, 11:00:00 GMT+0
Resolved - This incident has been resolved..

]]>