A Backblaze offline message calls for checking the existing backup client's schedule, connectivity, and transfer progress before rebuilding anything. Preserve the backup set, distinguish a VPN from an unsupported proxy, and confirm that the original queue resumes and the latest backup time advances after any change.

Key Takeaways:

An old backup time and an active connection failure are related observations, not identical diagnoses.

Backblaze documents VPN use separately from proxy use.

Keep the existing backup set and queue intact during comparison.

Recovery requires client transfer and backup-time progress, not just access to the website.

Step 1: What does the Backblaze offline message actually show?

Open the installed backup client's control panel and record the exact status, latest backup time, and current schedule. Note the computer identity and client version so you do not accidentally inspect another machine's backup in the web account. Keep your local files in place and do not uninstall the client as the first diagnostic action.

Confirm that the computer has been awake, connected to a permitted network, and available during its configured backup period. If you expected progress while the machine was asleep or disconnected, first provide an ordinary opportunity for the configured task to run.

Protect the original backup relationship. Do not delete the backup, start an unrelated new backup, or use inheritance or migration options merely because the status looks stale. Those operations address machine and backup identity, not the isolated question of whether the existing task can transfer data.

Keep a record that can explain the next result

Write down the visible queue or remaining-data information, if the client provides it, and whether there is a specific connection error. Record the time you start observing. Do not compare queue snapshots while adding many files to the backup scope.

The device and application diagnosis guide helps if the computer itself is unstable. The cloud transfer direction checks cover wider file-service failures. This workflow preserves the original Backblaze operation.

Step 2: Is Backblaze backup not connecting, or is the task waiting?

Give the existing task one normal opportunity to run according to its schedule. Observe whether the client reports transmission, remains idle, or produces a reproducible connectivity message. Keep the application's configured backup scope unchanged so you can interpret the result.

Check official service information for the relevant backup product when a service interruption is plausible. A working web account does not prove the backup endpoint works. Likewise, a status page with no incident does not prove your local application has permission to connect.

Observation	What it tells you	Next action
Client is waiting outside its schedule	The task may not have attempted a transfer	Observe during an allowed backup period
Client reports offline during an attempted backup	A connection problem needs investigation	Record the exact error and access controls
Website opens but the queue is unchanged	Browser access alone is inconclusive	Inspect the backup client's own result
Client transfers and backup time advances	The original operation is progressing	Verify expected file availability

How should you inspect security software?

Backblaze's offline support article identifies firewall blocking as a possible cause of a long gap in backup activity. Use that as a prompt to inspect the client's allowed outbound access with the responsible owner. Do not conclude that every old backup time is caused by the firewall.［1］

The official article includes temporary disabling as a troubleshooting suggestion. Here, keep protection active and ask for a narrowly scoped rule review instead of turning off the firewall or antivirus wholesale. On a managed computer, report the failed backup application and timestamp to the administrator.

Preserve TLS validation and account protection. Investigate certificate or authentication errors without silencing them. If official service information indicates an ongoing interruption, pause route changes and watch the original task when service is restored.

Step 3: Are you using a supported Backblaze VPN backup path or a proxy?

Inventory the connection method before adding another layer. Record whether the computer uses a system VPN, a browser-only proxy, a manual system proxy, or a setup script. On managed equipment, you may not own those settings; identify their administrator before changing them.

Backblaze's support guidance says its PC Online Backup software can operate over a VPN, while proxy use is unsupported and can cause backup failures. This is a compatibility distinction, not a speed or uptime guarantee. A browser proxy and a system VPN do not become interchangeable merely because both can change a browser's apparent path.［2］

For Windows, use the proxy setting identification procedure to distinguish automatic setup and manual configuration. Record the existing values securely before any permitted local change. Never publish a proxy URL containing a user name or password with your troubleshooting record.

What if a VPN is already active?

If policy permits, disconnect the existing VPN and observe the same backup task under its normal schedule. If direct access resumes transmission, record that outcome and investigate the prior VPN configuration. A problem created by an existing route is not a reason to automatically recommend another service.

If a proxy is mandatory, ask the network owner for a supported way for this backup client to access its service. Do not remove organization controls or assume a personal VPN authorizes an alternative. If you cannot obtain a permitted compatible path, stop the experiment and give the owner the client status and official compatibility information.

Keep other changes out of this comparison. Do not update the client, change file exclusions, attach a different disk, and toggle the network simultaneously. Each may affect the queue or timing; a useful record identifies which variable changed.

Step 4: Can the original queue transmit through an authorized route?

Proceed only if the client has had time to run, no service or account issue explains the failure, and an unresolved public connection problem remains. Choose a comparable observation period with the computer awake. Keep the backup set, selected files, and schedule unchanged, and record the direct result first.

For an existing queue stalled by that connection problem, AethoVPN offers a route comparison on the backup computer. Use Pro or Premium: Windows uses the official installer, while Mac uses the website configuration guide with a VPN client and Pro or Premium. Select an available nearby location, enable global mode, then let the same Backblaze task run and watch its transfer state and latest backup time without creating or inheriting a backup.

A different route cannot repair file exclusions, a sleeping computer, account problems, or a server interruption. If the queue remains stalled or performance worsens, disconnect and preserve the comparison instead of cycling through locations. If you need a new account for this controlled queue test, start the 3-day Pro trial; it is available once per user.

Separate a connection test from a speed claim

Record whether transmission starts and whether the client reports progress, rather than promising a shorter overall backup. Different files, local preparation, and a changing queue can make elapsed-time comparisons misleading. This workflow does not establish a throughput benchmark or a general recommendation for every slow backup.

Use the baseline and VPN verification checklist to keep your route observations organized. Its connection checks do not prove Backblaze restored the task. A new IP or reachable website is only a preliminary observation, while actual client progress is the relevant result.

Respect local law, network policy, and the service's conditions. Check the current network and plan terms before a large transfer; do not assume any traffic or speed entitlement from this troubleshooting procedure. End the comparison if your chosen path is not permitted or a new trust or account error appears.

Step 5: Has backup progress become verifiable?

Compare the client's status and latest backup time with your baseline. A reduced queue can be encouraging, but it is not sufficient if files were removed from the selected scope. Check that you are still observing the same computer and original backup relationship.

Use a harmless, already intended backup file as an additional end-to-end check. When the client indicates that its backup has completed or progressed appropriately, inspect that file's expected availability through the official account's normal restore-browsing workflow. Do not overwrite the local original or launch a broad restore solely to validate connectivity.

If a specific file is absent despite general progress, inspect its selection, exclusion, and current status separately. Do not delete the backup set to make the totals look consistent. Connection restoration and coverage of every desired file are different acceptance questions, and both matter to a dependable backup.

How do you distinguish partial progress from recovery?

Record client transmission, backup-time advancement, queue observation, and the chosen file's availability in separate fields. If transmission resumes but the timestamp has not advanced, keep observing or investigate the client state before declaring completion. If the timestamp advances but your expected file is absent, retain that narrower unresolved finding.

For a persistent failure, send official support the client version, operating system, schedule, last successful backup time, sanitized error, and permitted route results. Mask computer identifiers, private file paths, account details, and any secret configuration. Share full logs only through a trusted support channel and only after checking their contents.

Stop making changes when the original task progresses and the intended file check is satisfied. Also stop if a concrete service, policy, authentication, or trust issue takes ownership of the problem. Restore temporary route changes that are unnecessary for the regular schedule, and keep a short record in case the same offline message returns.

Summary

Inspect schedule, awake time, and the actual backup-client message.
Preserve the original backup set and identify VPN versus proxy use.
Compare only an authorized route while keeping the queue and selected data stable.
Verify transmission, backup-time advancement, and intended file availability separately.

FAQ

Does an old backup time mean Backblaze is currently offline?

Not necessarily. The computer may not have attempted a backup during the expected period. Check awake time, schedule, and the client's present connection result before assigning a cause.

Can the website work while the backup client cannot connect?

Yes. Website access and the installed client's transfer are separate checks. Observe the original task and capture its actual result rather than using account login as proof of backup progress.

Is a system proxy equivalent to a VPN for Backblaze?

No. Backblaze documents VPN operation separately and says proxy use is unsupported. Identify the actual connection method and obtain a permitted compatible path if a proxy is mandatory.［2］

Should I delete or inherit a backup to clear the offline status?

No. Those actions change the backup relationship and are not justified by an isolated connection fault. Preserve the existing set and investigate its schedule, access, and transfer state first.

Does a VPN guarantee that a slow backup becomes faster?

No. A route comparison checks whether the existing client can transmit under the observed conditions. It does not measure general speed or resolve local file processing and service-side work.

What is the smallest useful recovery check?

Confirm the same client resumes transfer and its backup time advances, then inspect one harmless intended file through the official restore browser. Keep the local original and backup relationship unchanged.

When should I escalate instead of changing routes again?

Escalate when the task repeatedly fails across permitted paths or produces account, certificate, policy, or service errors. Provide the schedule and sanitized client observations instead of rebuilding the backup.

Sources

Backblaze Help — Backblaze hasn't backed up in a long time and is reporting that it is offline. Why? — https://help.backblaze.com/hc/en-us/articles/217664558-Backblaze-hasn-t-backed-up-in-a-long-time-and-is-reporting-that-it-is-offline-Why
Backblaze Help — Can I back up over a VPN or Proxy? — https://help.backblaze.com/hc/en-us/articles/360024200294-Can-I-back-up-over-a-VPN-or-Proxy

Sources checked 7 October 2026.

Backblaze Offline: Restore the Backup Connection