Standards Backed Fax Status Checks for Senders

Your fax status lives in three places: the online fax dashboard’s sent list and delivery receipt, the physical machine’s confirmation page, or an API status response if you send programmatically. A successful transmission typically shows “OK,” “Success,” or “Delivered.” If you see anything else, the status will include an error code that tells you whether to retry, check the number, or contact the recipient directly.

TL;DR:

Most fax statuses are updated within seconds to a few minutes depending on the sending method, with physical machines showing almost immediate results.

Error codes like no answer, busy signals, or communication errors usually indicate line or recipient issues, advising retries or direct contact.

Delivery confirmations only prove the fax was received by the machine, not that it was printed or read, and should be supplemented with a follow-up for critical documents.

Programmatic tracking relies on job IDs, status updates, and real-time notifications via polling or webhooks, with logs essential for troubleshooting delays.

Confirming actual receipt for important documents requires pairing delivery receipts with direct recipient acknowledgment, especially for legal or time-sensitive transmissions.

Where to check fax status: dashboards, confirmation pages, and device logs

The right place to look depends on how you sent the fax. If you used an online fax service, your account dashboard holds a “Sent” list with a delivery receipt for each transmission. Check the timestamp, current status, page count, and job ID to confirm the document reached its destination.

If you sent from a physical fax machine, the device can print a Transmission Verification Report, or you can review the Fax Journal for a log of recent activity. According to Brother’s support documentation, this report lists the recipient number, date, time, duration, page count, and a result code. A successful send shows “OK.” A failed one shows “NG” or “ERROR.”

Integrated printer-fax devices often add a third option: email receipts or a “Sent” folder tied to the device’s internal memory. These work the same way as a paper report but save you from standing at the machine.

Timing varies by method:

Online services usually show status within seconds to a couple of minutes for standard transmissions.
A queued status means the system is waiting for an open line or completing automatic retries.
Physical machines show status almost immediately after the call completes, successful or not.

Common status messages and error codes: how to read them

Most fax systems cycle through a small set of statuses: Queued, Sending, In Progress, Success or Delivered, and Failed or Error. Queued means the job is waiting its turn. Sending or In Progress means the call is active. Success or Delivered confirms the recipient machine accepted the full transmission.

When a fax fails, the error code tells you why. Here are the most common ones and what to do:

No Answer means the receiving line never picked up. Wait a few minutes and retry, or confirm the number is correct.
Busy means the line was occupied during the attempt. Most services or machines will retry automatically within a short window.
Communication Error usually points to a line quality issue or an incompatible machine. Try resending at a different time or through an alternate line.

You can find these codes in the fax log on your machine, in the API response from an online service, or on the printed confirmation page. According to Canon’s support guidance, checking the communication log helps you decide whether to wait and retry, double-check the number, or call the recipient to confirm their line is working.

Pro Tip: Write down the error code before you retry. If the same code repeats twice, the problem is almost always the number or the line, not a one-time glitch.

Delivery confirmation vs processing confirmation: what each one guarantees

A delivery confirmation tells you the receiving fax machine accepted the transmission. It does not tell you whether anyone printed, opened, or read the document. This distinction comes from how internet fax standards separate the two concepts. According to RFC 2532, Delivery Status Notifications confirm that a message reached its destination, while Message Disposition Notifications confirm that the recipient processed it, and recipients are free to ignore MDN requests entirely.

The extended fax draft specification reinforces this: senders can request both notification types, but only the DSN is close to guaranteed.

For routine business use, a delivery receipt is usually enough. For legal filings, medical records, or anything time-sensitive, follow up with a phone call or email to confirm the recipient actually processed the document, since a delivery receipt alone cannot prove that.

Step-by-step troubleshooting when a fax is delayed or failed

When a fax does not go through, work through these checks in order:

Verify the recipient’s fax number, including the area code and any required dialing prefix.
Confirm the document format and page count match what you intended to send.
Check the confirmation receipt for the exact duration and status code, not just a pass or fail flag.
For “Busy” or “No Answer” codes, wait several minutes and retry, or try sending at a different time of day.
For repeated “Communication Error” codes, contact the recipient to confirm their line is active, try an alternate fax number, or switch to an online fax service as a fallback.

If the fax repeatedly fails for the same recipient, the problem is often on their end, a shared line, an out-of-paper machine, or a disconnected number.

Pro Tip: Keep the confirmation page or digital receipt any time you fax something that might matter later. It records the timestamp, page count, and recipient number, which is accepted as practical proof of transmission if a dispute ever comes up.

Tracking programmatically: status endpoints, polling, and webhooks

If you send faxes through code, your status response should include a few essential fields: job ID, current status, timestamp, page count, and an error code when applicable, typically returned as JSON or XML. According to Concord’s developer documentation, real-time status methods can also report pages sent so far while a job is still in progress.

You have two main ways to get status updates:

Polling means your application repeatedly calls a status endpoint on a schedule. This works well for checking many jobs at once.
Webhooks mean the fax provider pushes a status update to your system the moment it changes, which gives you near-instant notification without constant checking.

For a batch of faxes, query a multi-job status endpoint rather than looping through individual job IDs one at a time, since this cuts down on both requests and rate-limit risk. Automated notification systems built for other industries follow a similar pattern: Trustico’s tracking notifications use the same event-driven logic to alert users the moment a status changes.

When you display status to end users, log every state change with its timestamp so you can trace a failed job back to the exact error code that caused it.

What actually matters when you need to be sure a fax arrived

Delivery confirmation is the baseline, not the finish line. A receipt showing “OK” tells you the recipient’s machine accepted the transmission, nothing more. For anything with real consequences, a tax deadline, a signed contract, a time-stamped legal filing, I treat that receipt as step one and a phone call or email as step two.

Pairing a delivery receipt with direct recipient acknowledgment closes the gap that standards like RFC 2532 point out: delivery and processing are not the same event, and no fax system can promise both.

— Engin

How PerPageFax helps you confirm your fax actually arrived

We built our fax service around the idea that confirming delivery should not require an account, a subscription, or guesswork. Every fax sent through our service comes with a delivery confirmation, so you can check the sent list and see the exact status without digging through settings or waiting on a monthly report.

Here’s what that looks like in practice:

We send faxes with encryption and automatic retries if the first attempt hits a busy signal or a no-answer.
Our service shows a per-page delivery confirmation so you know the transmission succeeded, not just that it was queued.
Our service charges a per-page fee with no hidden fees. Testing a resend or trying a fallback number costs you exactly what you’d expect.
If a fax fails, we refund it.

If you need to send a document now and want to see the confirmation yourself, send your fax online and check the delivery status as soon as it completes.

FAQ

How to check fax status?

Check your online fax service’s sent list or delivery receipt, or print a Transmission Verification Report or Fax Journal directly from a physical fax machine. Both show a status label such as “OK,” “Success,” or an error code if the transmission failed.

Can you track a fax?

Yes. Most online fax services provide a dashboard showing each fax’s status, timestamp, and page count, while physical machines log the same details in a printable journal. Developers can also pull status through an API that returns job ID, status, and error codes in real time.

How do you know if a fax is successful?

A successful fax shows a status like “OK,” “Success,” or “Delivered” on your confirmation page, receipt, or dashboard. According to Brother’s support guidance, a failed transmission instead shows “NG” or “ERROR” along with a code explaining why.

Why is it taking so long for my fax to go through?

A fax that stays in a queued state is usually waiting for an open line or going through automatic retries after a busy signal or no-answer. If the delay continues past a few minutes, check the communication log for an error code that points to the actual cause.