- Service Status
- /
- MyCase

Is MyCase Down?
- 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
| Component | Status |
|---|---|
| MyCase the service itself | Operational |
| Integrations | Operational |
| Mobile Applications | Operational |
| MyCase eCheck Payments | Operational |
| MyCase Credit Card Payments | Operational |
| Recent Activity, History and Notification Emails | Operational |
FlareWarden checks
mycase.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- 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
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 57 ms | 4 ms | 16 ms | 100 ms |
| Dallas | 127 ms | 25 ms | 29 ms | 217 ms |
| Frankfurt | 44 ms | 2 ms | 10 ms | 77 ms |
| Newark | 172 ms | 10 ms | 14 ms | 217 ms |
| Paris | 37 ms | 9 ms | 26 ms | 110 ms |
| Stockholm | 117 ms | 1 ms | 56 ms | 216 ms |
| Sydney | 142 ms | 1 ms | 7 ms | 575 ms |
| Toronto | 155 ms | 11 ms | 23 ms | 219 ms |
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 streakMeasured 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.
Related services
MyCase outage FAQ
Is MyCase down or just payments?
A client says their payment failed. Were they charged?
Why did I stop getting MyCase notifications?
Does a MyCase outage affect the mobile app?
Is MyCase down for everyone or just me?
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
403or429means 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


