Skip to content

Outage tracker

Notarize: incident history

The last 24 hours in detail, Notarize's declared incident record, and our regional check results beside it.

← Back to Notarize's check readings

We started checking Notarize on November 2, 2026, which is 7 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when Notarize reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Notarize's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Notarize's own status page declared. Below it, any public chatter we saw about Notarize and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Notarize's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Unverified user reportsNo reports about Notarize in the last 24 hours, which is not evidence that nothing is wrong.
Notarize's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Notarize's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Notarize next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East100.00%725
US-West99.82%560
Europe100.00%515
Asia-Pacific100.00%307

Their declared record

Notarize's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Issue adding documents to a transactionPartial outage
Jul 20, 2026, 4:08 PM UTC to Jul 20, 2026, 10:09 PM UTC (6h 1m)resolved
their latest update (Jul 20, 2026, 10:09 PM UTC): This incident has been resolved.
Degraded PerformanceMinor incident
Jul 14, 2026, 4:59 PM UTC to Jul 14, 2026, 7:20 PM UTC (2h 20m)resolved
their latest update (Jul 14, 2026, 7:20 PM UTC): No new occurrences of the issue have been identified during the monitoring period. The issue has been resolved.
Document completion delays on Proof platformPartial outage
Apr 8, 2026, 8:25 PM UTC to Apr 8, 2026, 9:07 PM UTC (42 min)resolved
their latest update (Apr 8, 2026, 9:07 PM UTC): This incident has been resolved.
Proof platform - real estate closing incident due to eVault service outagePartial outage
Feb 20, 2026, 2:01 AM UTC to Feb 20, 2026, 2:32 AM UTC (31 min)resolved
their latest update (Feb 20, 2026, 2:32 AM UTC): This incident has been resolved.
Degraded performance with identity verificationMinor incident
Feb 4, 2026, 8:39 PM UTC to Feb 4, 2026, 9:16 PM UTC (38 min)resolved
their latest update (Feb 4, 2026, 9:16 PM UTC): The vendor has resolved the issue. Our service is functioning normally now.
Retroactive update: credential analysis errors on Proof platformPartial outage
Jan 15, 2026, 3:30 PM UTC to Jan 15, 2026, 3:30 PM UTC (0 min)resolved
their latest update (Jan 15, 2026, 3:30 PM UTC): On January 15th 2026, between 10:35 and 11:05 am ET, Proof platform experienced elevated error rates when handling credential analysis. This prevented most signers from entering a meeting with a notary. We observed a recovery after 11:05 am ET.
Issue with 3rd-party services impacting eNotesMinor incident
Dec 12, 2025, 12:37 AM UTC to Dec 12, 2025, 1:43 AM UTC (1h 6m)resolved
their latest update (Dec 12, 2025, 1:43 AM UTC): This incident has been resolved.
Delays in Processing DocumentsMinor incident
Nov 17, 2025, 9:17 PM UTC to Nov 17, 2025, 11:50 PM UTC (2h 33m)resolved
their latest update (Nov 17, 2025, 11:50 PM UTC): The issue has been resolved.
Performance impact on Proof platformMajor outage
Oct 20, 2025, 12:50 PM UTC to Oct 20, 2025, 10:08 PM UTC (9h 18m)resolved
their latest update (Oct 20, 2025, 10:08 PM UTC): This incident has been resolved. We observe full recovery of the Proof platform. We apologize for the inconvenience this incident has caused.
Degraded functionality on Proof platform - notification of past incidentMinor incident
Oct 20, 2025, 7:00 AM UTC to Oct 20, 2025, 7:00 AM UTC (0 min)resolved
their latest update (Oct 20, 2025, 7:00 AM UTC): Earlier today, Proof platform experienced an incident due to a major outage at our cloud provider as well as several impacted vendors. Proof application remained available but a few features such as SMS MFA and certain identity verification flows were affected. We were unable to …

Showing the 10 most recent of 50 incidents Notarize has declared in the history we hold.

These entries are Notarize's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

Notarize's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.