Oxylabs Network Outage History

27 incidents recorded over the last 365 days, 27 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Oxylabs Network status99.96% uptime history

Every Recorded Oxylabs Network Incident

Oxylabs Network incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 26, 2026Scraper API and Web Unblocker OutageThe incident has been fully resolved and all normal operations have resumed. We apologize for the disruption and appreciate your patience while our team worked to address the issue.11 minResolved
Aug 13, 2026Datacenter Proxies OutageThe Datacenter Proxies outage is now fully resolved. We apologize for the inconvenience and appreciate your patience throughout the resolution process.4h 0mResolved
Jul 28, 2026Dashboard login issuesThe dashboard login issue has been resolved. Thank you for your patience.38 minResolved
Jun 19, 2026Scraper API & Web Unblocker showing degraded success ratesSuccess rates for Google scrapers across Scraper API & Web Unblocker services have now stabilized. Thank you for your patience.4h 38mResolved
Jun 3, 2026Push-Pull, WU and Proxy Integration experiencing degraded success rates and high response time for Google sourcesThis incident has been resolved.4h 9mResolved
Jun 3, 2026Realtime, WU and Proxy Integration showing degraded success rates and increased response timesThis incident has been resolved.1h 18mResolved
May 29, 2026Load Balancing IssueOxylabs experienced a service outage from 10/25/16:30 GMT+3 to 10/25/19:00 GMT+3. The outage was caused by a Cloudflare issue with their API services, which impacted our infrastructure monitoring and thus disrupted…-1363318 minResolved
May 29, 2026Full service outage for Real-Time Crawler and Next-Gen Residential ProxiesThe issue was caused by a bug in one of the system components, which in turn resulted in API outage. The bug has since been fixed to prevent this type of outage happening again.-2882854 minResolved
May 29, 20262024-04-25 System OutageDuring maintenance of the authentication caching service cluster, issues with electing a new master appeared. The cluster lost its master and the new master couldn’t be selected for 14 minutes. This led to a complete…-1099948 minResolved
May 29, 2026Session monitoring introducedProxy session monitoring has been introduced with slightly too sensitive outage logic. Proxies are fully operational and monitoring logic has been adjusted.-1111471 minResolved
May 29, 2026Scraper API and Web Unblocker outageScraper APIs and Web Unblocker experienced an outage from 2024-03-13 12:30 GMT+3 to 2024-03-13 13:10 GMT+3. The reason was a collapse of a critical component cluster due to network instability. The cluster was brought…-1161806 minResolved
May 29, 2026Scraping Logic ChangeScraping logic changes caused increased load on the system, which affected job completion time. Changes were reverted and we are working on prevention of similar situations happening in the future.-1254208 minResolved
May 29, 2026Upstream Provider DowntimeAt 2023-12-15 01:52 UTC, due to server issues in one of Oxylabs upstream providers, the European infrastructure faced service downtime. Traffic was routed through other locations in North America to ensure business…-1290718 minResolved
May 29, 2026Proxies Rotator OverloadAt 2023-12-14 13:03 UTC Changes on the target website resulted in increased retry attempts, subsequently causing an overload in one of the system’s components. The incident was resolved by lowering scrapers’ qos (aka…-1291498 minResolved
May 29, 2026False incident notification for DC ProxiesOn June 22nd and 23rd false incident notification was created for DC proxies due to service monitoring misconfiguration issue. DC users were fully able to use our service.-1012412 minResolved
May 29, 2026Temporary US Entrypoint OutageWe have observed a temporary US Entrypoint outage for Shared DC proxies. Incident lasted for 5 minutes-1043798 minResolved
May 29, 2026Search Engine Performance IssuesThis incident has been resolved.-1047958 minResolved
May 29, 2026Scraper API IssuesThis incident has been resolved.-1053989 minResolved
May 29, 2026Issues Scraping Search EngineNo problems were detected on our end. It seems that Google Search experienced some issues from their side. We have observed Google's downtime recorded on Is google.com down or not working properly? Check current status…-1091098 minResolved
May 29, 2026Scraper API IssuesService was affected due to internal misconfiguration issue. Now it has been fully restored.-989116 minResolved
May 29, 2026Degraded ScraperAPI performanceService has fully stabilised and incident has been resolved.-1003354 minResolved
May 29, 2026False incident notification for Residential ProxiesOn July 1st false incident notification was created for Residential proxies due to service monitoring misconfiguration issue. Residential Proxy users were fully able to use our service during this period.-1003829 minResolved
May 29, 2026EU Infrastructure service degradeDue to 3rd party server issues, EU infrastructure faced a service degradation. Incident was resolved once the vendor mitigated the outage.-903898 minResolved
May 29, 2026Scraper API Temporary OutageScraper API faced a temporary outage. The incident was caused by network issues (packet loss) in one of the servers. Issue was resolved within 9 minutes.-904978 minResolved
May 29, 2026Degraded Performance of EU Residential Proxy PerformanceIncident has been resolved after reverting the code changes.-948674 minResolved
May 29, 2026Scraper API OutageEarlier released changes caused cache service to overload over time, bringing down the cache service. Without the cache service Realtime and Proxy Endpoint integration methods, as well as Web Unblocker, couldn’t serve…-953878 minResolved
May 29, 2026Lag in DC Usage MetricsDatacenter proxy usage metrics are now up to date-958450 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Oxylabs Network incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Oxylabs Network Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Oxylabs Network acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Oxylabs Network outage in this window ran 4h 38m, against a mean recovery of 2h 29m. If you depend on Oxylabs Network in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.