Capacity logo

Is Capacity Down?

SaaSLive status, outages, and incident history

No. Capacity is up right now.

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

OperationalChecked just nowLive · 60s while moving1 active incident

Know the moment Capacity breaks

Capacity is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

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

How we know: the official Capacity status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Capacity Component Status

The main Capacity systems on this page. All 29 are operational right now.

29operational
Analytics
Operational
Answer Engine
Operational
Articles
Operational

26 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Automations, AWS ec2-us-east-1, AWS eks-us-east-1, AWS elasticache-us-east-1, AWS elb-us-east-1, AWS kafka-us-east-1, AWS kms-us-east-1, AWS mq-us-east-1, AWS rds-us-east-1, AWS textract-us-east-1, AWS vpc-us-east-1, CapacityDB, and 14 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Capacity Outages & Incidents

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

Capacity Agents IncidentStarted Sep 25, 2026Investigating

A fix has been implemented and we are monitoring the results. --- [2026-09-25T08:13:13.776-05:00] (investigating) We are currently investigating an issue with our Agents service.

IP Change: Capacity's Developer PlatformScheduled for Sep 24, 2026 · 24h 0mScheduled

The scheduled maintenance has been completed. --- [2026-09-23T22:18:07.227-05:00] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-09-23T20:01:12.198-05:00] (scheduled) Maintenance will begin as scheduled in 60 minutes. --- [2026-09-16T16:49:00.651-05:00] (scheduled) Capacity's Developer Platform, which makes API calls to third party services, will change its IP on September 23, 2026 at 9pm CDT. If your organization uses allowlists to permit API calls from Capacity, you need to add the new IP to your allowlist before the cutover. We recommend keeping both IPs allowlisted until the transition is fully complete. If the allowlist isn't updated in time, requests from Capacity to your applications may fail starting September 23, 2026 at 9pm CT. For the new IP address, you can email support@capacity.com.

Change to Outbound IP for Dev PlatformResolved Sep 11, 2026 · 50 minResolved

This has been delayed two weeks until 9/23. We will be reaching out to impacted customers shortly with details. --- [2026-09-10T19:33:34.979-05:00] (monitoring) The outbound IP from which our Dev Platform product makes API calls to third party services will unexpectedly change shortly, due to a maintenance related restart. Most customers will be completely unaffected by this, other than a short disruption to any outbound calls through Dev Platform at 9pm CDT. However, some customers have allowlisted this IP and will need to make updates to their network. Please reach out to your Customer Success representative if you believe you will be affected and need details. We will be reaching out to customers ourselves shortly as well.

Capacity Uptime History

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

Uptime history49 days observed
Aug 899.74% average · 7 days with incidentsSep 25

Live Capacity Outage Reports

Problems reported by engineers using Capacity. 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 Capacity problems reported yet.

Something wrong with Capacity on your end?

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

About Capacity

Capacity publishes a public status page at status.capacity.com covering 29 components, including Concierge, SMS and Voice. PulsAPI tracks Capacity outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Capacity uptime at 99.99%. Response times, incident history, and SLA tracking for Capacity are available on the PulsAPI dashboard.

Capacity Status FAQ

Is Capacity down right now?

The verdict at the top of this page comes from the latest poll of the official Capacity status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Capacity 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 Capacity recovers.

How do I check Capacity uptime history?

PulsAPI tracks Capacity uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.99%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Capacity changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Capacity outages?

PulsAPI reads the official Capacity status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Capacity components?

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

Can I get alerts when Capacity goes down?

Yes. Create a free account and subscribe to Capacity: 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 Capacity 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 Capacity problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Capacity?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Capacity 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 Capacity with the rest of your stack

2463+ 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