- Detected by Pingoru
- Jun 15, 2026, 02:14 PM UTC
- Resolved
- Jun 16, 2026, 03:59 PM UTC
- Duration
- 1d 1h
Affected: Western Europe ISP
Timeline · 3 updates
-
investigating Jun 15, 2026, 02:14 PM UTC
We're investigating a connectivity issue affecting a subset of our ISP proxy IP ranges in Belgium. Customers using affected ranges may experience failed or degraded connections; other European ranges and all other regions are unaffected. We're working with our upstream provider to restore service and will share further updates as we learn more.
-
identified Jun 15, 2026, 05:18 PM UTC
We've identified the cause as an issue with our upstream provider affecting a subset of our ISP ranges in Belgium. Most affected ranges have now been restored; a small number remain affected and we are working with our provider on full restoration. We will share further updates as we learn more.
-
resolved Jun 16, 2026, 03:59 PM UTC
Resolved — the affected Belgium ISP ranges have been restored and service is operating normally. A small number of legacy ranges are being retired; customers on those ranges will be migrated to replacement ranges or credited. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 12:19 PM UTC
- Resolved
- Jun 09, 2026, 07:32 PM UTC
- Duration
- 1d 7h
Affected: North America ISPNorth America DC
Timeline · 2 updates
-
investigating Jun 08, 2026, 12:19 PM UTC
We are investigating a partial outage affecting a subset of our North America ISP and Datacenter proxy ranges. Affected customers may be unable to connect to proxies hosted on one of our US servers. Workaround: affected customers can be issued a replacement proxy on a different server for immediate restoration of service. Please contact our support team and we will provision a replacement right away. Because this is a server-level outage dependent on our upstream provider, full restoration may take an extended period - potentially more than 12 hours. We will share further updates as we learn more. We apologize for the inconvenience.
-
resolved Jun 09, 2026, 07:32 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 07, 2026, 04:42 AM UTC
- Resolved
- Jun 08, 2026, 11:53 AM UTC
- Duration
- 1d 7h
Affected: Africa ISP
Timeline · 3 updates
-
investigating Jun 07, 2026, 04:42 AM UTC
We are investigating a connectivity issue affecting ISP proxy endpoints in Botswana, Mozambique, Namibia, South Africa, and Zimbabwe. Customers using proxies in these locations may experience connection failures or timeouts. Proxies in all other regions are operating normally. Our team is actively investigating, and we will share further updates as we learn more.
-
identified Jun 07, 2026, 04:54 AM UTC
We have identified the issue as an infrastructure failure affecting one of our upstream servers, which has taken the proxy endpoints serving Botswana, Mozambique, Namibia, South Africa, and Zimbabwe offline. Our upstream provider is working to restore the affected server. Proxies in all other regions remain unaffected, and we will share further updates as we learn more.
-
resolved Jun 08, 2026, 11:53 AM UTC
This incident has been resolved. Connectivity to the affected ISP proxy endpoints in Botswana, Mozambique, Namibia, South Africa, and Zimbabwe has been restored and services are operating normally. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 11:11 PM UTC
- Resolved
- Jun 06, 2026, 05:15 AM UTC
- Duration
- 6h 4m
Affected: North America ISP
Timeline · 3 updates
-
investigating Jun 05, 2026, 11:11 PM UTC
We are investigating a connectivity issue affecting a portion of our ISP proxies in the United States, caused by an outage at one of our upstream providers. Affected endpoints may be unreachable or fail to establish connections. Other regions and product lines are operating normally. Our team is engaged with the upstream provider to restore service, and we will share further updates as we learn more.
-
monitoring Jun 06, 2026, 04:20 AM UTC
Connectivity to the affected ISP proxies in the United States has been restored and endpoints are reachable again. We are monitoring to confirm full stability before marking this incident resolved.
-
resolved Jun 06, 2026, 05:15 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 03:24 AM UTC
- Resolved
- Jun 05, 2026, 04:08 AM UTC
- Duration
- 43m
Affected: Residential Proxies JP
Timeline · 3 updates
-
investigating Jun 05, 2026, 03:24 AM UTC
We are investigating reports of degraded performance (increased latency and reduced throughput) on our Japan residential proxy pool. Some connections may be slower than usual. Other residential regions are unaffected.
-
monitoring Jun 05, 2026, 03:44 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 05, 2026, 04:08 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2026, 01:06 AM UTC
- Resolved
- Jun 04, 2026, 10:12 AM UTC
- Duration
- 9h 5m
Affected: Residential APIResidential Proxies USResidential Proxies EUResidential Proxies SGResidential Proxies JPResidential Proxies AU
Timeline · 3 updates
-
investigating Jun 04, 2026, 01:06 AM UTC
We are currently investigating reports of degraded performance across our Residential Proxy network. Customers may experience slower connection speeds, increased latency, or intermittent connection failures when using residential proxies. Our team is actively investigating the cause and working to restore normal service. We will share further updates as we learn more.
-
identified Jun 04, 2026, 04:14 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Jun 04, 2026, 10:12 AM UTC
This incident has been resolved. Residential Proxy performance has returned to normal across all regions, and our monitoring confirms stable service. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 05:30 AM UTC
- Resolved
- May 27, 2026, 07:36 AM UTC
- Duration
- 2h 6m
Affected: North America ISP
Timeline · 2 updates
-
investigating May 27, 2026, 05:30 AM UTC
We are investigating reduced availability affecting a subset of our ISP proxies in the United States (New York region). Affected endpoints may be unreachable or returning intermittent errors. Our team is engaged with our upstream provider to restore service.
-
resolved May 27, 2026, 07:36 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 25, 2026, 01:43 PM UTC
- Resolved
- May 25, 2026, 07:17 PM UTC
- Duration
- 5h 34m
Affected: North America ISP
Timeline · 3 updates
-
identified May 25, 2026, 01:43 PM UTC
We are investigating an issue affecting a portion of our ISP proxy ranges in the United States. Customers routing through the affected US ISP proxies may currently experience connection failures or timeouts. Other regions and product lines are not affected.
-
identified May 25, 2026, 01:43 PM UTC
We are continuing to work on a fix for this issue.
-
resolved May 25, 2026, 07:17 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 06:22 AM UTC
- Resolved
- May 20, 2026, 09:05 AM UTC
- Duration
- 2h 42m
Affected: Asia ISPAsia DC
Timeline · 4 updates
-
investigating May 20, 2026, 06:22 AM UTC
We are investigating reports of degraded connectivity affecting a subset of our ISP and Data Center proxies in Asia, with impact observed for endpoints in Singapore, Thailand, Vietnam, Malaysia, Indonesia, and the Philippines. Customers in other regions are unaffected. Our team is actively investigating and we will share further updates as we learn more.
-
identified May 20, 2026, 07:24 AM UTC
The issue has been identified and a fix is being implemented.
-
identified May 20, 2026, 09:04 AM UTC
We are continuing to work on a fix for this issue.
-
resolved May 20, 2026, 09:05 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 09:25 AM UTC
- Resolved
- May 19, 2026, 11:47 AM UTC
- Duration
- 2h 22m
Affected: Africa DC
Timeline · 3 updates
-
investigating May 19, 2026, 09:25 AM UTC
We are experiencing unexpected downtime with our Datacenter proxies in South Africa. Location: South Africa Detected: 2026-05-19 08:00 UTC Our team is actively working to resolve this issue and restore functionality as quickly as possible. We apologize for the inconvenience this may cause and appreciate your understanding.
-
identified May 19, 2026, 09:25 AM UTC
We are currently experiencing a large-scale DDoS attack affecting parts of our network infrastructure. We understand the disruption this causes and are treating this as a priority incident. Some customers may experience intermittent connectivity issues, increased latency, or timeouts while mitigation work continues. Our technical teams are actively working with our DDoS mitigation and upstream network partners to manage the impact. We will continue to share updates as the situation develops.
-
resolved May 19, 2026, 11:47 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 16, 2026, 05:35 PM UTC
- Resolved
- May 16, 2026, 05:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 16, 2026, 05:35 PM UTC
We are currently investigating a partial outage affecting a subset of our Datacenter IPs in the Baltic region (Lithuania, Latvia, Estonia). Some customers may experience reduced availability or connectivity issues on the affected addresses. Other regions are not impacted. Our upstream providers has been notified and we will share further updates as we learn more.
Read the full incident report →
- Detected by Pingoru
- May 16, 2026, 09:45 AM UTC
- Resolved
- May 16, 2026, 01:14 PM UTC
- Duration
- 3h 28m
Affected: Southern America ISP
Timeline · 2 updates
-
investigating May 16, 2026, 09:45 AM UTC
We are investigating a partial outage affecting our ISP Proxies product in the Brazil region. A subset of endpoints is currently degraded; other regions and products are unaffected.
-
resolved May 16, 2026, 01:14 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 07:15 PM UTC
- Resolved
- May 07, 2026, 04:42 AM UTC
- Duration
- 9h 27m
Timeline · 2 updates
-
investigating May 06, 2026, 07:15 PM UTC
We are experiencing unexpected downtime with our ISP proxies in United States. Location: United States Detected: 2026-05-06 17:00 UTC Our team is actively working to resolve this issue and restore functionality as quickly as possible. We apologize for the inconvenience this may cause and appreciate your understanding.
-
resolved May 07, 2026, 04:42 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 08:19 AM UTC
- Resolved
- Apr 29, 2026, 01:15 PM UTC
- Duration
- 4h 56m
Timeline · 2 updates
-
investigating Apr 29, 2026, 08:19 AM UTC
There's upcoming scheduled maintenance for our DCH proxies. Location: Greece, Turkey, Israel, Bulgaria, Egipt, Saudi Arabia, Jordan From: 2026-04-29 08:00 UTC To: 2026-04-29 11:00 UTC During this period, proxies based in this location may be intermittently unavailable. We appreciate your understanding and apologize for any inconvenience this may cause.
-
resolved Apr 29, 2026, 01:15 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 03:00 PM UTC
- Resolved
- Apr 21, 2026, 03:20 PM UTC
- Duration
- 19m
Affected: Western Europe ISP
Timeline · 3 updates
-
identified Apr 21, 2026, 03:00 PM UTC
We are experiencing unexpected downtime with our ISP proxies in NL. Location: NL Detected: 2026-04-21 01:52:48 PM Our team is actively working to resolve this issue and restore functionality as quickly as possible. We apologize for the inconvenience this may cause and appreciate your understanding.
-
identified Apr 21, 2026, 03:01 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Apr 21, 2026, 03:20 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 01:24 PM UTC
- Resolved
- Apr 21, 2026, 02:24 PM UTC
- Duration
- 59m
Affected: Southern America ISPSouthern America DC
Timeline · 2 updates
-
investigating Apr 21, 2026, 01:24 PM UTC
We are currently experiencing unexpected technical difficulties with our DHCP/ISP Static proxies. Our team is actively working to resolve this issue and restore functionality as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience while we address this matter.
-
resolved Apr 21, 2026, 02:24 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 02:15 AM UTC
- Resolved
- Apr 21, 2026, 02:15 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 21, 2026, 02:25 AM UTC
We're pleased to inform you that the issues with our EU Residential proxies have been resolved, and the service is now fully operational.
Read the full incident report →
- Detected by Pingoru
- Apr 19, 2026, 07:01 AM UTC
- Resolved
- Apr 19, 2026, 08:07 AM UTC
- Duration
- 1h 6m
Affected: Western Europe ISP
Timeline · 2 updates
-
investigating Apr 19, 2026, 07:01 AM UTC
We are experiencing unexpected downtime with our ISP proxies in Europe. Location: Europe Detected: 2026-04-19 03:30:00 UTC Our team is actively working to resolve this issue and restore functionality as quickly as possible. We apologize for the inconvenience this may cause and appreciate your understanding.
-
resolved Apr 19, 2026, 08:07 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 05:16 AM UTC
- Resolved
- Apr 17, 2026, 08:27 AM UTC
- Duration
- 3h 10m
Affected: Southern America ISP
Timeline · 2 updates
-
investigating Apr 17, 2026, 05:16 AM UTC
We are experiencing unexpected downtime with our ISP proxies in South America. Location: South America Detected: 2026-04-17 04:20:00 UTC Our team is actively working to resolve this issue and restore functionality as quickly as possible. We apologize for the inconvenience this may cause and appreciate your understanding.
-
resolved Apr 17, 2026, 08:27 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 09:04 AM UTC
- Resolved
- Apr 16, 2026, 11:51 AM UTC
- Duration
- 2h 46m
Affected: North America ISPNorth America DC
Timeline · 2 updates
-
identified Apr 16, 2026, 09:04 AM UTC
Our team is actively working to resolve this issue and restore functionality as quickly as possible. We apologize for the inconvenience this may cause and appreciate your understanding.
-
resolved Apr 16, 2026, 11:51 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 07:52 AM UTC
- Resolved
- Apr 09, 2026, 08:22 AM UTC
- Duration
- 29m
Affected: Southern Europe ISP
Timeline · 2 updates
-
investigating Apr 09, 2026, 07:52 AM UTC
We are currently experiencing a minor outage affecting ISP proxies in Spain due to an ISP-level issue. A subset of Spain exit nodes may be temporarily unavailable or degraded. Affected resources are being migrated to alternative infrastructure. We expect full restoration shortly. We will provide updates as the situation progresses. We apologize for any inconvenience.
-
resolved Apr 09, 2026, 08:22 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 04, 2026, 11:50 AM UTC
- Resolved
- Apr 04, 2026, 09:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 04, 2026, 11:50 AM UTC
We experienced degraded performance and a partial outage with our US Residential proxies. During this time, requests to US endpoints returned an increased number of 504 errors. The issue has now been fully resolved. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 02:48 PM UTC
- Resolved
- Mar 18, 2026, 10:22 AM UTC
- Duration
- 19h 34m
Timeline · 4 updates
-
investigating Mar 17, 2026, 02:48 PM UTC
We are experiencing unexpected downtime with part of our our ISP proxies in United states. Location: United States Detected: 2026-03-17 14:10 UTC Our team is actively working to resolve this issue and restore functionality as quickly as possible. We apologize for the inconvenience this may cause and appreciate your understanding.
-
identified Mar 17, 2026, 06:22 PM UTC
The issue has been identified. The majority of prefixes are back online, and our team is continuing to work on restoring the remaining ones.
-
monitoring Mar 18, 2026, 05:12 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 18, 2026, 10:22 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 11:55 AM UTC
- Resolved
- Mar 18, 2026, 05:12 AM UTC
- Duration
- 17h 16m
Affected: Asia DC
Timeline · 2 updates
-
investigating Mar 17, 2026, 11:55 AM UTC
We are currently experiencing reduced subnet visibility affecting a portion of our Datacenter proxy pool in Asia. As a result, some proxies in this region may be unreachable or returning limited results. Location: Asia Detected: 2026-03-17 10:00 UTC Our team is actively investigating the issue and working to restore full subnet visibility as quickly as possible. We apologize for the inconvenience this may cause and appreciate your understanding.
-
resolved Mar 18, 2026, 05:12 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 07:37 PM UTC
- Resolved
- Mar 10, 2026, 09:11 PM UTC
- Duration
- 1h 33m
Affected: Residential Proxies USResidential Proxies EUResidential Proxies SGResidential Proxies JP
Timeline · 4 updates
-
identified Mar 10, 2026, 07:37 PM UTC
We are currently experiencing unexpected technical difficulties with our Residential proxies. Our team is actively working to resolve this issue and restore functionality as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience while we address this matter.
-
identified Mar 10, 2026, 07:39 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Mar 10, 2026, 08:12 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 10, 2026, 09:11 PM UTC
This incident has been resolved.
Read the full incident report →