Is Pickrr Down?
Yes, we are detecting problems with Pickrr that began 1 minute ago.
Service returned HTTP 0. Error: Connection timeout or resolution failure: cURL error 28: Connection timed out after 8002 milliseconds (see https://curl.se/libcurl/c/libcurl-errors.html) for https://www.pickrr.com
Real-time Incident Detection Chart
Spikes in user reports (line) mapped against status page traffic baseline (bars) detect outages via Z-score analysis.
Community Status Activity
Recent user-submitted feedback and problems reported.
Loading recent activity...
Troubleshooting Pickrr Issues
Pickrr Troubleshooting Guide
If you're experiencing issues with Pickrr (the logistics and shipping management platform), try these troubleshooting steps:
Basic Steps
- 1. Refresh your dashboard & clear browser cache. Pickrr's web app relies heavily on up-to-date session data. Press Ctrl + F5 (Windows) or Cmd + Shift + R (Mac) to force-reload. Clear cached images and files from your browser settings (last 24 hours) to remove stale shipment tracking widgets.
- 2. Test with a different browser or incognito mode. If you are using an extension that blocks pop-ups or scripts, the Pickrr shipping label preview and rate calculator may fail. Open the site in an incognito/private window or try a secondary browser (e.g., Chrome vs. Firefox).
- 3. Verify your login session and API key status. If you are logged out or your API token has expired (common for Pickrr integrations), you will see "401" errors or blank screens. Log out, log back in, and regenerate your API key from the seller panel if you use the Pickrr API.
- 4. Check your internet connection specifically for large payloads. Pickrr's shipment manifest and bulk order uploads can be heavy. Run a speed test (aim for 10+ Mbps download) and disable any VPN or proxy that might interfere with the request to api.pickrr.com endpoints.
- 5. Confirm your payment/wallet balance. If you are blocked from creating shipping labels, ensure your Pickrr wallet has sufficient funds. An unpaid invoice or low balance can cause silent failures on the "Create Shipment" button.
Intermediate Steps
- 1. Verify courier partner availability for your pin code. Pickrr aggregates multiple courier partners (Delhivery, Blue Dart, etc.). If you suddenly cannot generate a label for a specific order, check whether the destination pin code has temporary service restrictions. Try a different courier partner manually under "Rate Calculator" to isolate the issue.
- 2. Inspect the browser console for blocked third-party requests. Open Developer Tools (F12) > Network tab and reload the page. Look for any failed requests to cdn.pickrr.com or track.pickrr.com. If you see CORS errors or 503 responses, the issue is on Pickrr's side, not your local machine. Also, check the Console tab for JavaScript errors from tracking scripts.
- 3. Update your integration or plugin. If you use Pickrr with Shopify, WooCommerce, or a custom API, ensure the plugin version is current. Often, a recent platform update breaks the webhook from Pickrr. Re-sync your orders via the plugin settings or regenerate the webhook URL in your store admin.
- 4. Test the Pickrr API directly. If the web dashboard loads fine but your order import fails, try hitting the Pickrr API health endpoint (like /v2/ping or /health) using a tool like Postman. If you get a timeout, the issue is server-side. If you get a 200 but wrong data, the issue is your local cache or formatting.
Still not working?
If you have completed all the steps above and Pickrr is still not loading shipments, creating labels, or syncing orders, the outage is likely on their infrastructure. Please click the "Report Outage" button on this Is It Down Bro? status page so we can track the outage in real-time and notify you once Pickrr is back online.
Troubleshooting & FAQs
Recent Pickrr Outages
Helpline Info
Support details
Embeddable Status Badge
Add this dynamic SVG status shield to your customer docs, readme, or dashboard.
Status Methodology
Outage Detection: We check website availability using network scanners every minute. If a response fails, we perform automated retries.
Community Reporting: Spikes in user reports are analyzed via standard deviations (Z-score). Z-scores above 2.0 indicate a high likelihood of a localized or major outage.
Geolocating: Crowdsourced feedback tracks country origins using public IP-API geo databases to map the scope of outages.