Formal logo

Is Formal Down?

SecurityLive status, outages, and incident history

No. Formal is up right now.

Every monitored Formal system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Formal breaks

Formal is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Formal status page
How we know: the official Formal status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Formal Status Summary

As of 15:19 UTC on 14 November 2026, Formal is operational. PulsAPI checked Formal's official status page and found 2 of 2 components operational, with no active incidents. The latest incident, "Database Load Issues", was on Aug 24, 2026 and lasted 4h 28m.

Cite as: PulsAPI, “Formal status”, checked 14 November 2026, 15:19 UTC. https://www.pulsapi.com/services/formal

Formal Component Status

The main Formal systems on this page. All 2 are operational right now.

2operational
Formal APIs
Operational
Formal Control Plane
Operational

Component statuses may change independently during partial outages.

Recent Formal Outages & Incidents

Incident history from the official Formal status page, including resolution updates.

Database Load IssuesResolved Aug 24, 2026 · 4h 28mResolved

The database load issue has been fixed and incident has been resolved --- [2026-08-24T22:47:52Z] (monitoring) Though we are seeing database issues clear up and functionality being restored we are working through any downstream impact. We'll continue monitoring to ensure full resolution. --- [2026-08-24T22:19:28Z] (monitoring) We have deployed a fix for the database load and monitoring for resolution. --- [2026-08-24T22:00:56Z] (monitoring) We are continuing to work on the database load issue and are actively monitoring to ensure resolution. --- [2026-08-24T20:23:11Z] (identified) Formal is experiencing a high database load which is causing API timeouts. We have identified the root cause of the issue and are actively working on fixing it.

Formal Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Formal incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Formal Outage Reports

Problems reported by engineers using Formal. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Formal problems reported yet.

Something wrong with Formal on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Formal

Formal posts its status at status.formal.ai. The page covers 2 components, among them Formal APIs and Formal Control Plane. Past incidents and uptime for Formal stay on this page, which helps when you want to know how often it has trouble.

Formal Status FAQ

Is Formal down right now?

The verdict at the top of this page comes from the latest poll of the official Formal status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Formal is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Formal recovers.

How do I check Formal uptime history?

PulsAPI tracks Formal uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Formal changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Formal outages?

PulsAPI reads the official Formal status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Formal components?

Yes. PulsAPI monitors 2 individual Formal components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Formal goes down?

Yes. Create a free account and subscribe to Formal: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Formal to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Formal problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Formal?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Formal plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Formal with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services