Skip to main content
MyCase logo

Is MyCase Down?

No — MyCase is up
MyCase's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 266 ms

Right now

The verdict is the worse of these two. How we decide

MyCase's status page

status.mycase.com · read · checked every 3 minutes

Operational
MyCase's components, as its status page reports them
ComponentStatus
MyCase the service itselfOperational
IntegrationsOperational
Mobile ApplicationsOperational
MyCase eCheck PaymentsOperational
MyCase Credit Card PaymentsOperational
Recent Activity, History and Notification EmailsOperational

FlareWarden checks

mycase.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
266 ms
Checked

By region

  • Amsterdam reachable, 121 ms
  • Dallas reachable, 321 ms
  • Frankfurt reachable, 92 ms
  • Newark reachable, 277 ms
  • Paris reachable, 149 ms
  • Stockholm reachable, 315 ms
  • Sydney reachable, 592 ms
  • Toronto reachable, 261 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam57 ms4 ms16 ms100 ms
Dallas127 ms25 ms29 ms217 ms
Frankfurt44 ms2 ms10 ms77 ms
Newark172 ms10 ms14 ms217 ms
Paris37 ms9 ms26 ms110 ms
Stockholm117 ms1 ms56 ms216 ms
Sydney142 ms1 ms7 ms575 ms
Toronto155 ms11 ms23 ms219 ms
We check that mycase.com loads, not every feature behind it. Test it yourself

History

Incidents MyCase reported

Since Oct 22, 15 days · from status.mycase.com

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

MyCase website availability

Measured by FlareWarden · mycase.com

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
385ms

Last 30 days

50-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 31 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 29 checks
Oct 18: 100.00% uptime, 31 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of mycase.com from multiple regions every 6 hours. MyCase's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 50 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What MyCase does

MyCase is legal practice management software for law firms, covering cases, clients, documents, billing and payments in one place. Firms use it to track matters, communicate with clients through a portal, record time and collect fees by card or eCheck. It holds both the case file and the firm's receivables, so an outage stops casework and cash collection together.

What an outage looks like

MyCase will not load or sign in. Case records, documents and client messages do not open. Integrations with other tools stop syncing. The mobile apps fail to refresh. Card and eCheck payments do not process, so clients paying an invoice see an error. Activity history and notification emails stop, so nobody is told about new messages or events.

What to do about it

Check status.mycase.com, which lists the main MyCase application separately from Integrations, Mobile Applications, eCheck Payments, Credit Card Payments and the activity, history and notification email component. If only payments are affected, tell clients who report errors to try again later rather than paying another way that is harder to reconcile against the invoice.

Is it down for everyone, or just you?

If this page says MyCase is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

MyCase outage FAQ

Is MyCase down or just payments?
Look at the rows on status.mycase.com. MyCase reports Credit Card Payments and eCheck Payments as components separate from the main application, so a client can fail to pay an invoice while your staff use MyCase normally. If one payment method is affected, the other may still work, and you can point clients to it.
A client says their payment failed. Were they charged?
Check before they try again. A failed attempt should not complete, but a client who retries several times can end up with more than one payment. Once the payment components are operational, look at the invoice's payment history in MyCase, confirm what actually went through, and refund any duplicates before the client notices them on a statement.
Why did I stop getting MyCase notifications?
MyCase tracks Recent Activity, History and Notification Emails as one component, separate from the application. If it is degraded, messages and events still reach MyCase but the emails that tell you about them do not. Log in and check client messages and upcoming events directly until the component recovers.
Does a MyCase outage affect the mobile app?
Mobile Applications is its own component on the status page. The apps can fail while the web version works, or keep working while one web feature is down. If the app will not refresh, try MyCase in a browser before assuming the service is down, and check whether an app update is pending.
Is MyCase down for everyone or just me?
Compare the status page with this page's regional measurements. If both show MyCase healthy, the likely cause is local: your office network, a browser extension, or a stale session. If our probes fail to reach MyCase from several regions at once, the problem is on MyCase's side.

How we measure this

  • We request MyCase's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where MyCase publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of MyCase itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when MyCase goes down

We check MyCase every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required