Skip to content
PulseWatchOUTAGE.INTEL
Convex logo

Other

Is Convex down right now?

NormalOfficial status last polled Oct 12, 2026 06:18 UTCconvex.devOfficial status page

Are you on the Convex team and see something inaccurate? Report it to us. We respond within one business day.

Is Convex down right now?

No. Convex has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 12, 2026 06:35 UTC

Normal

Convex is operating normally

As of Oct 12, 2026 06:35 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

0

Last incident

Oct 10, 2026 01:42 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Convex.

2

Incident days

28

No recorded incident

2h 56m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Convex. Hover a day for detail.

Sep 13Sep 18Sep 23Sep 28Oct 3Oct 801234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

2

Days with incidents

1 incident

Busiest day

2h 56m

Recorded duration

Report volume

0 reports in last 24H

06:30 AM10:00 AM01:30 PM05:00 PM08:30 PM12:00 AM03:30 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Convex: vendor-reported major incident on October 9 (tracked 2h 56m)

Oct 9, 10:45 PM → Oct 10, 01:42 AM · 2h 56m · high

Convex reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked this incident for 2h 56m, closing it on 2026-10-10T01:42:18.727Z.

Duration
2h 56m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The incident is known from Convex's own status page.

Incident timeline

  1. Oct 9, 10:45 PM

    The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it

  2. Oct 9, 10:45 PM

    Status updated: possible issue

  3. Oct 10, 01:42 AM

    PulseWatch closed the incident

Official updates

  1. Oct 9, 10:45 PM

    Convex reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.

Reliability

Detected by PulseWatch

30-day uptime

99.59%

90-day uptime

99.79%

Calculated from Convex's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedHigh

Convex: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Convex or have an alert rule on it can be alerted, labelled vendor-reported.

10/9/2026, 10:45:44 PM · 2h 56m

10:45 PM01:42 AM
Detection10/9/2026, 10:45:44 PM · 2d ago

Detected — high severity

Convex: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Convex or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedMedium

Convex incident correlated across 1 signal group: official/vendor.

8/16/2026, 11:39:15 PM · 1h 33m

11:39 PM01:13 AM
Detection8/16/2026, 11:39:15 PM · 1mo ago

Detected — medium severity

Convex incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Convex enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

convex.dev