Skip to main content
Proof logo

Is Proof Down?

No — Proof is up
Proof's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 175 ms

Right now

The verdict is the worse of these two. How we decide

Proof's status page

status.proof.com · read · checked every 3 minutes

Operational
Proof's components, as its status page reports them
ComponentStatus
Notarize Consumer App (iOS)Operational
Proof Consumer (Web)Operational
Notarize Consumer App (Android)Operational
Proof/Notarize APIOperational
Proof Real EstateOperational
Notary PlatformOperational

FlareWarden checks

proof.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
175 ms
Checked

By region

  • Amsterdam reachable, 108 ms
  • Dallas reachable, 114 ms
  • Frankfurt reachable, 111 ms
  • Newark reachable, 107 ms
  • Paris reachable, 107 ms
  • Stockholm reachable, 227 ms
  • São Paulo reachable, 304 ms
  • Toronto reachable, 324 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam40 ms3 ms11 ms101 ms
Dallas58 ms2 ms8 ms110 ms
Frankfurt60 ms2 ms9 ms104 ms
Newark60 ms2 ms9 ms101 ms
Paris52 ms2 ms13 ms101 ms
Stockholm55 ms17 ms22 ms185 ms
São Paulo228 ms3 ms17 ms296 ms
Toronto261 ms1 ms9 ms320 ms
We check that proof.com loads, not every feature behind it. Test it yourself

History

Incidents Proof reported

Since Nov 4, 2 days · from status.proof.com

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

Proof website availability

Measured by FlareWarden · proof.com

Last 7 days
—
Last 30 days
—
Last 90 days
—
Avg response, 30 days
—

Last 30 days

Oct 7: no data
Oct 8: no data
Oct 9: no data
Oct 10: no data
Oct 11: no data
Oct 12: no data
Oct 13: no data
Oct 14: no data
Oct 15: no data
Oct 16: no data
Oct 17: no data
Oct 18: no data
Oct 19: no data
Oct 20: no data
Oct 21: no data
Oct 22: no data
Oct 23: no data
Oct 24: no data
Oct 25: no data
Oct 26: no data
Oct 27: no data
Oct 28: no data
Oct 29: no data
Oct 30: no data
Oct 31: no data
Nov 1: no data
Nov 2: no data
Nov 3: no data
Nov 4: 100.00% uptime, 16 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of proof.com from multiple regions every 6 hours. Proof's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 2 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Proof does

Proof verifies identities and secures transactions online, including notarization with a live notary; its consumer apps still carry the Notarize name. Signers meet a notary in an online meeting, real estate closings run on Proof Real Estate with eNotes and vaulted documents, and businesses connect through its API. Its status page lists the Notarize iOS and Android apps, Proof Consumer on the web, the Proof/Notarize API, Proof Real Estate and the Notary Platform.

What an outage looks like

Many incidents delay completed documents after a notary meeting or e-signing, usually when a certificate or digital signing vendor fails, as on September 2, 2025 for about 5.4 hours. Others stop signers entering a meeting: on July 14, 2026 some recipients did not receive their KBA questions, and on January 15 credential analysis errors kept most signers out for 30 minutes. On July 20 users could not add documents to new transactions for about six hours.

What to do about it

Check status.proof.com for your product: the Notarize apps, Proof Consumer, the API, Proof Real Estate and the Notary Platform have separate rows. When completion is delayed, Proof has said documents will process automatically once the vendor recovers, and in November 2025 asked users not to use any force complete feature until the issue was resolved. Wait for completion rather than repeating the notarization.

Is it down for everyone, or just you?

If this page says Proof is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Proof outage FAQ

Do I need to redo my notarization if Proof's documents are delayed?
Proof's notices say no. In vendor outages that delayed completion, such as July 31, 2025, September 2, 2025 and April 8, 2026, it said affected documents would process automatically once the issue was fixed, and after July 31 that all backlogged documents were completed. In November 2025 it asked users not to use force complete features until the incident was resolved.
Is Notarize down or is it Proof?
Notarize is reported on Proof's status page. status.notarize.com redirects to status.proof.com, and the status page lists the Notarize consumer apps for iOS and Android beside Proof Consumer on the web and the Proof/Notarize API. An outage named on one of these rows covers the Notarize apps too.
Why can't I get into my notary meeting on Proof?
Identity checks before the meeting are a common cause. On July 14, 2026 a fault at Proof's primary KBA provider meant some signers did not receive knowledge-based authentication questions for about 2.3 hours, delaying or blocking entry to meetings. On January 15 credential analysis errors kept most signers out from 10:35 to 11:05 am ET, and on February 4 an identity verification vendor slowed some transactions.
Does a Proof outage affect real estate closings?
Some do. On February 19, 2026 an eVault service outage hit some real estate closings for about 30 minutes, and on December 11, 2025 a third-party fault affected creating and completing transactions with eNotes and vaulted documents for about an hour. Proof Real Estate has its own row on the status page, so check it beside the Notary Platform row.

How we measure this

  • We request Proof's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Proof publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Proof itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Proof goes down

We check Proof every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required