testRigor logo

Is testRigor Down?

SaaSLive status, outages, and incident history

No. testRigor is up right now.

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

OperationalChecked 3m agoLive · every 60s

Know the moment testRigor breaks

testRigor 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 testRigor status page
How we know: the official testRigor status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

testRigor Status Summary

As of 13:06 UTC on 10 November 2026, testRigor is operational. PulsAPI checked testRigor's official status page and found 3 of 3 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for testRigor, counting degraded performance as up. The latest incident, "Scheduled maintenance", was on Sep 16, 2026 and lasted 17 min.

Cite as: PulsAPI, “testRigor status”, checked 10 November 2026, 13:06 UTC. https://www.pulsapi.com/services/testrigor

testRigor Component Status

The main testRigor systems on this page. All 3 are operational right now.

3operational
API services
Operational
app.testrigor.com
Operational
Test executors
Operational

Component statuses may change independently during partial outages.

Recent testRigor Outages & Incidents

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

Scheduled maintenanceResolved Sep 16, 2026 · 17 minResolved

Maintenance has been concluded, test cases can be executed as usual. --- [2026-09-16T09:21:51.427-07:00] (monitoring) Our services are undergoing maintenance. For the time being test cases won't be able to run. --- [2026-09-16T09:20:36.750-07:00] (monitoring) Our services are undergoing maintenance. For the time being test cases won't be able to run.

Test cases stuck in queueResolved Sep 11, 2026 · 5h 0mResolved

The issue has been fixed, and test cases should be executing as expected. --- [2026-09-11T14:54:47.849-07:00] (monitoring) A fix for the issue has been implemented, and is currently being monitored. --- [2026-09-11T13:53:04.032-07:00] (identified) The issue has been mitigated. The root cause has been identified, we're currently working on a permanent fix. --- [2026-09-11T13:15:18.580-07:00] (investigating) Test cases won't be able to start. Still investigating the issue. --- [2026-09-11T12:09:58.392-07:00] (investigating) The issue has resurfaced, test cases are stuck in queue. We continue to investigate the root cause of the problem --- [2026-09-11T11:32:18.889-07:00] (investigating) Test cases are now executing normally. We are still investigating for root cause --- [2026-09-11T10:58:02.192-07:00] (investigating) Some test cases have started to execute. Still investigating the root cause --- [2026-09-11T10:46:23.471-07:00] (investigating) We are currently investigating the issue to find the cause of the problem

testRigor Uptime History

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

Uptime history91 days observed
Aug 12100.00% average · 1 day with incidentsNov 10

Going further back: testRigor uptime by month and every recorded testRigor outage.

Live testRigor Outage Reports

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

Something wrong with testRigor on your end?

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

About testRigor

testRigor exposes 3 monitored components on its status page at status.testrigor.com — app.testrigor.com, API services and Test executors among them. Follow testRigor downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

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

testRigor Status FAQ

Is testRigor down right now?

The verdict at the top of this page comes from the latest poll of the official testRigor 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 testRigor 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 testRigor recovers.

How do I check testRigor uptime history?

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

How fast does PulsAPI detect testRigor outages?

PulsAPI reads the official testRigor 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 testRigor components?

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

Can I get alerts when testRigor goes down?

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

Is there a free way to monitor testRigor?

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

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