- Service Status
- /
- Proof

Is Proof Down?
- 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
| Component | Status |
|---|---|
| Notarize Consumer App (iOS) | Operational |
| Proof Consumer (Web) | Operational |
| Notarize Consumer App (Android) | Operational |
| Proof/Notarize API | Operational |
| Proof Real Estate | Operational |
| Notary Platform | Operational |
FlareWarden checks
proof.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- 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
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 40 ms | 3 ms | 11 ms | 101 ms |
| Dallas | 58 ms | 2 ms | 8 ms | 110 ms |
| Frankfurt | 60 ms | 2 ms | 9 ms | 104 ms |
| Newark | 60 ms | 2 ms | 9 ms | 101 ms |
| Paris | 52 ms | 2 ms | 13 ms | 101 ms |
| Stockholm | 55 ms | 17 ms | 22 ms | 185 ms |
| São Paulo | 228 ms | 3 ms | 17 ms | 296 ms |
| Toronto | 261 ms | 1 ms | 9 ms | 320 ms |
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
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.
Related services
Proof outage FAQ
Do I need to redo my notarization if Proof's documents are delayed?
Is Notarize down or is it Proof?
Why can't I get into my notary meeting on Proof?
Does a Proof outage affect real estate closings?
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
403or429means 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


