Is Check down?

Last checked 7m ago
Current status
Check is up

No incidents right now.

Get alerts when Check breaks →

Free · no credit card

Official status page: https://status.checkhq.com · Polled every 5 minutes · 4 components tracked

Real-time Check status, recent outages, and incident history — pulled directly from Check's official status page at https://status.checkhq.com every 5 minutes. Pingoru tracks 4 Check services and has captured 5 incidents in the last 90 days (97.08% uptime). Get email, Slack, Discord, or webhook alerts the moment Check reports a new incident — free for 5 monitors, no credit card.

Users who monitor Check also follow these Finance services: Affirm QuickBooks PayRange Avalara Plaid Robinhood Xero Zuora Bill.com Xero Developer Platform View all 6,000+ providers
Check uptime 97.08% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Degraded API Availability + Performance
    Resolved 7h 24m
    Started Apr 28, 2026, 08:37 AM UTC · Resolved Apr 28, 2026, 04:01 PM UTC
    APIConsole
    3 updates · show timeline
    • investigating · Apr 28, 2026, 08:37 AM UTC

      We've identified an event impacting AVI availability and performance inconsistency. Investigation in progress.

    • monitoring · Apr 28, 2026, 08:45 AM UTC

      The system is recovering. We are actively monitoring to ensure it remains recovered. Root cause analysis to follow.

    • resolved · Apr 28, 2026, 04:01 PM UTC

      4/28 — Resolution Update and RCA Impact and duration: From approximately 1:05 AM PT to 1:44 AM PT on Tuesday, April 28 (~40 minutes), API endpoints across the platform returned elevated error rates and Console pages were intermittently unavailable. Health checks returned to green at 1:44 AM PT and the system has been stable since. What happened: Two scheduled background jobs ran simultaneously in the early-morning window and pushed our cache layer past its memory limit. Once the cache filled, normal cache writes began failing globally, which surfaced as the broad API degradation. Today's root cause is distinct from the SEV-2 on Friday, 4/24, which was driven by an inbound webhook volume spike from a banking partner. We traced today's failures directly to cache memory pressure, not webhook volume. Going forward: We are taking immediate steps to prevent recurrence, including reducing the load these scheduled jobs place on the cache layer and improving how the system handles cache pressure so it degrades gracefully rather than producing errors. We are also strengthening monitoring on cache health and related signals so this class of issue is caught before it impacts API availability.

    Latest: 4/28 — Resolution Update and RCA Impact and duration: From approximately 1:05 AM PT to 1:44 AM PT on Tuesday, April 28 (~40 minutes), API endpoints across the platform returned ele…

  2. Spikes in Check API Latency and Errors
    Resolved 7h 36m
    Started Apr 24, 2026, 01:33 PM UTC · Resolved Apr 24, 2026, 09:10 PM UTC
    APIConsole
    3 updates · show timeline
    • investigating · Apr 24, 2026, 01:33 PM UTC

      We identified spikes in API latency and errors. Investigation in progress.

    • investigating · Apr 24, 2026, 01:36 PM UTC

      System is recovering. We are still investigating this issue to understand root cause and therefore prevent recurrence, as well as assessing potential impact.

    • resolved · Apr 24, 2026, 09:10 PM UTC

      This issue has been resolved. This morning Check experienced a database overload from increased webhook traffic that spiked for a a period of time on the morning of 4/24, and surfaced as high latency and error count. The team identified the issue, resolved the immediate database load concerns and restored functionality. The Check engineering team will be following up promptly with a resolution to prevent recurrence.

    Latest: This issue has been resolved. This morning Check experienced a database overload from increased webhook traffic that spiked for a a period of time on the morning of 4/24, and surfa…

See the full Check outage history

2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 3 incidents
  • Degraded API Availability + Performance Resolved
    Started Apr 28, 2026, 08:37 AM UTC · Resolved Apr 28, 2026, 04:01 PM UTC · 7h 24m
  • Spikes in Check API Latency and Errors Resolved
    Started Apr 24, 2026, 01:33 PM UTC · Resolved Apr 24, 2026, 09:10 PM UTC · 7h 36m
  • Service degradation impacting Production and Sandbox Resolved
    Started Apr 09, 2026, 01:25 PM UTC · Resolved Apr 09, 2026, 04:45 PM UTC · 3h 19m

See Check in your Pingoru dashboard

Monitor Check alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Check to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Check incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Check or see every provider at once.

Maintenance calendar

Scheduled Check maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Check status change, one inbox

Pingoru watches Check's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Check reports on 4 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Check alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Check maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Check services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Check from the same account, with per-user notification preferences for any monitor.

Get notified on Check status changes

Pingoru watches Check's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Check free

Monitor Check along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Check and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Check uptime & incident history

See 90 days of Check uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Check uptime history

Frequently asked questions

What is Check's uptime?
Over the last 90 days, Check reported 97.08% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.checkhq.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Check's uptime history rolling forward in real time.
Has Check had outages in 2026?
Yes — Check has had 4 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Check outage?
The most recent Check incident was "Degraded API Availability + Performance", which started on April 28, 2026 and was resolved on April 28, 2026. Pingoru captured this directly from https://status.checkhq.com. See the full incident card above for affected components and the update timeline.
How often does Check have outages?
Based on the last 90 days, Check averages 1.3 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Check's status page?
Check's official status page is https://status.checkhq.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Check down right now?
Check is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Check reports a change. Current status is based on 4 tracked services.
How does Pingoru know if Check is down?
We read https://status.checkhq.com directly, using Check's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Check has an outage?
Create a free Pingoru account and add Check as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Check's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Check incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Check issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Check status?
We use Check's own status page at https://status.checkhq.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked Check components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Check's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Check free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →