Is Shadowfax Down?
No, we are not detecting any problems with Shadowfax right now.
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 Shadowfax Issues
Shadowfax Troubleshooting Guide
If you're experiencing issues with Shadowfax, try these troubleshooting steps:
Basic Steps
- 1. Verify your internet connection. Shadowfax relies heavily on real-time GPS and data syncing between the rider app, client dashboard, and dispatch servers. Ensure you have a stable 4G/5G or Wi-Fi connection. Run a quick speed test and try loading other websites or apps to confirm the problem is specific to Shadowfax.
- 2. Force-close and restart the Shadowfax app. Whether you are a delivery partner using the rider app or a business using the client dashboard, a fresh start clears temporary glitches. Swipe the app away from your recent apps list and reopen it after 10 seconds.
- 3. Clear the app cache and data. For Android/iOS rider apps, go to Settings > Apps > Shadowfax > Storage and tap "Clear Cache." For the web dashboard, clear your browser's cache and cookies. This resolves issues like stuck order statuses, pins not updating, or delayed notifications.
- 4. Check your device's location settings. Shadowfax delivery tracking depends on accurate GPS. Make sure location services are enabled for the app (Settings > Location > Shadowfax > "While Using the App") and that you have granted precise location permission, not just approximate.
- 5. Try a different browser or device. If you are using the Shadowfax web dispatch panel, test the same account on a different browser (Chrome, Firefox, Edge) or another device. If the issue disappears, the problem is likely browser-specific or related to your local device memory.
Intermediate Steps
- 1. Check Shadowfax's known service disruptions. The most common cause of broad failures is a central server outage affecting the entire delivery ecosystem. If you are seeing "order not assigned," "live tracking frozen," or "rider location not updating" simultaneously for all orders, it is highly likely a platform-side backend issue rather than a local one.
- 2. Update the Shadowfax app to the latest version. Delivery partners frequently face login failures or crash loops after a server-side update if they are running an older app build. Visit the Google Play Store or Apple App Store, search for Shadowfax, and tap "Update." For the web platform, use an incognito window to bypass cached old JavaScript files.
- 3. Test with a different network (switch from Wi-Fi to mobile data, or vice versa). Enterprise clients often report that Shadowfax's API calls are blocked by office firewalls or strict corporate VPNs. Disconnect from a VPN, disable your firewall temporarily, or use a personal hotspot to see if the Shadowfax dashboard / rider app loads correctly.
- 4. Verify time and date synchronization. Shadowfax uses time-stamped tokens for order acceptance and delivery proof. If your device's clock is wrong by more than a few minutes, the app will reject actions like "Order Picked Up" or "Delivered." Go to Settings > System > Date & Time and enable "Automatic time zone and time."
Still having trouble?
If the steps above did not resolve the problem and Shadowfax remains non-functional for you, the issue is likely widespread. Please click the "Report Outage" button on this Is It Down Bro? status page. This will help us monitor the situation in real-time and inform other users if the outage is confirmed.
Troubleshooting & FAQs
Recent Shadowfax 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.