Pending means a newly created or reactivated monitor is waiting for its first completed check. Unknown means at least one check may have run, but Uptime Basics does not yet have enough reliable information to label the monitor Up or Down. No checks yet means no individual check records are available in the selected log range.
These messages are normal for a short time after creating or reactivating a monitor. They require attention when an active monitor remains unchanged beyond its expected check schedule.
What happens after creating a monitor
The scheduler must select the monitor, place its check into the processing queue, complete the HTTP request, and save the result. The dashboard then retrieves the saved state.
The monitor page displays Pending until the first completed check is stored. The first successful result changes it from Pending to Up. A first failure does not immediately label a new monitor Down. It changes to Unknown while the service applies regional and consecutive-failure confirmation, and changes to Down after three consecutive region-confirmed failed cycles.
For this reason, a failing five-minute monitor can move from Pending to Unknown and have failed rows in Detailed Logs before its overall status becomes Down.
How long to wait
Allow at least one complete configured interval plus the monitor's timeout and normal processing time for the first check to appear.
If the target is failing, allow enough time for three scheduled check cycles before expecting a confirmed Down status. A one-minute interval does not guarantee an exact one-minute update because requests, regional confirmation, queue processing, and dashboard refresh happen in addition to the schedule.
Check whether the monitor is active
Open Monitor Details and look at the current state:
- Active: scheduled availability checks should run.
- Paused: no new checks run until you activate it.
- Archived: the monitor does not run and does not appear in the normal active-monitor list.
- Automatically paused: repeated timeout protection or an account-level safeguard may have paused the monitor. Follow the notice before activating it again.
If you just activated or created the monitor, avoid pressing the control repeatedly. Wait for the confirmation and then allow one interval for a check.
Review Detailed Logs correctly
- Open the monitor.
- Open Monitor Tools, then Detailed Logs.
- Select Reset to use the last 24 hours with no status or diagnosis filters.
- Select Apply.
- Confirm that the selected time range includes the time when the monitor was created or activated.
Raw checks are retained for 30 days. A custom range outside that retention window cannot produce older raw rows.
If failed rows exist but the status is Unknown
This normally means the outage has not yet met the confirmation threshold. Check the Confirmation column:
- A primary failure can be rejected as an outage when other regions reach the site.
- A region-confirmed failure increases the consecutive-failure count.
- A successful cycle resets the consecutive-failure count.
- Three consecutive region-confirmed failures change the monitor to Down.
Do not change accepted HTTP codes simply to force an Up result. First confirm whether the response truly represents a healthy application.
If there are still no check rows
Confirm all of the following:
- The monitor is Active.
- The URL begins with
http://orhttps://and is the intended public endpoint. - The configured interval has elapsed since creation or activation.
- The selected log range and filters include the expected check time.
- The dashboard does not show an automatic-protection or service notice.
- The browser is online and the dashboard's Last update value is current.
Opening Monitor Details can help distinguish a delayed dashboard from missing check processing. Do not delete and recreate the monitor before collecting its monitor name, URL, creation time, interval, and visible state.
When to contact Support
Contact Support when an Active monitor has no Detailed Logs after more than one expected interval, or when Unknown remains after enough check cycles to determine a result.
Include:
- Monitor name and URL.
- Configured interval and timeout.
- Approximate creation or activation time.
- Current monitor state and dashboard Last update value.
- Whether Detailed Logs are empty or contain failed checks.
Never include passwords, verification codes, API keys, or full authorization-header values.