Overview
Zepeed supports multiple speedtest providers to give you flexibility in how you test your internet connection. After enabling providers, you can schedule automatic tests to run at regular intervals and track performance trends over time. Supported providers include:- Speedtest Ookla
- LibreSpeed
- Cloudflare
- Netflix (Fast.com)
Requirements
- Zepeed application is installed and running
- Admin or user access to the dashboard
- Internet connectivity for running speedtests
- Configured cron job for automated scheduler (see Scheduling section)
Enable a Provider
Zepeed supports multiple speedtest providers out of the box. Follow these steps to enable a provider.Navigate to Settings
From the dashboard, click your profile menu in the top right corner and select Settings.
Enable a provider
Click the Enable button next to the provider you want to use. The button will change to show the provider is now active.
Make sure your system has internet connectivity and your firewall allows outbound connections to the speedtest provider’s servers.
Scheduling
Configure automated speedtests to run on a schedule.Understanding schedules
Zepeed uses cron expressions to define when tests run. A cron expression has five fields:Create a schedule
Fill in details
Enter the following information:
- Name: A descriptive name (e.g., “Hourly Test”)
- Provider: Select which provider to use
- Cron Expression: Enter the cron pattern for when tests run
- Description (optional): Notes about this schedule
Common schedule examples
- Every 30 minutes
- Every hour
- Twice daily
- Every 4 hours
- Business hours
- Daily at 2 AM
- Weekly on Monday
Enable the scheduler
cron job is already configured in the docker imageManage schedules
View active schedules
In the Schedules section, you’ll see a list of all configured schedules with:- Schedule name
- Associated provider
- Cron expression
- Next run time
- Status (enabled/disabled)
Edit a schedule
Disable a schedule
Delete a schedule
Best practices
Stagger test times
Space out scheduled tests to avoid network congestion. Instead of all tests running at the top of the hour, use different minutes (e.g., 5, 25, 45).
Avoid peak hours
Schedule tests during off-peak times when possible to get more accurate baseline speeds. Avoid testing during busy work hours.
Test during consistent conditions
For meaningful comparisons, keep test conditions consistent. Run tests with similar network load and at regular intervals.
Monitor cron logs
Regularly check cron execution logs to ensure schedules are running as expected and catch issues early.
Use multiple providers
Enable multiple providers to get comprehensive data. Different providers may have different server locations and give you varied insights.
Review regularly
Check your dashboard frequently to spot performance trends, anomalies, or issues with specific providers.
Related pages
- Dashboard - View and interpret speedtest results
- Notifications - Get alerts for speed drops
- API Reference - Programmatic access to test data