Trust centre

Uptime targets and maintenance

The targets we run MyRecords Cloud to, how we plan maintenance, and how you will hear about problems.

2 min read Updated

Uptime targets on MyRecords Cloud

99.5%

Lite, Small, Medium

Allows about 3.6 hours of down time in a 30-day month.

99.9%

Large, with a standby database

Allows about 43 minutes in a 30-day month.

A health check every 5 minutes

Targets, not contract terms. Your order states what is promised.

In short

On MyRecords Cloud we aim for 99.5% uptime a month, and 99.9% on the Large plan, which has a standby database. These are targets, not the contract: your order states what is promised. Upgrades are planned with you and run outside your working hours.

Targets by plan

Uptime target for each MyRecords Cloud plan
PlanServerUptime targetDown time this allows in a 30-day month
Lite2 vCPU shared / 4 GB, Core bundle only, untested under load99.5%about 3.6 hours
Small2 vCPU / 8 GB, bundled database, 60 GB disk99.5%about 3.6 hours
Medium4 vCPU / 16 GB, bundled database, 100 GB disk99.5%about 3.6 hours
Large4 vCPU / 16 GB + managed database with standby (HA) + dedicated staging99.9%about 43 minutes

A target is what we run the service to and report against. It is not a contract term. The uptime promised to you, if any, is written in your order.

Maintenance

  • Upgrades are planned with you. We agree the time in advance and run them outside your working hours.
  • The system shows a maintenance notice while an upgrade runs. On our rehearsals an upgrade took 3 to 4 minutes, and rolling one back took 95 seconds.
  • Statutory changes (a new GST return format, for example) sometimes come with short deadlines. We may then ask for a shorter notice period, never without telling you.
  • Planned maintenance agreed with you does not count against the target.

How we watch

  • A health check runs every 5 minutes on each system: is the site answering, is there disk space, are background jobs and the scheduler running, and is the newest backup recent.
  • When a check fails, our team is alerted.

This monitoring has run on our test servers. The first pilot clients will be its first production use.

When something goes wrong

  • There is no public status page yet.
  • If a problem affects your system, we tell you directly, on your support ticket and by WhatsApp or e-mail, and again when it is fixed.
  • Restores follow the plan on backups and recovery.

Outside our control

  • Your internet connection and devices.
  • Government portals: GST, e-invoice and e-way bill. Files can still be prepared in MyRecords while a portal is down.
  • Providers you connect with your own account, such as WhatsApp Business, SMS or a payment gateway.

On your own server

Uptime depends on your machine, power and internet, and on whoever looks after the server. We can do that for you with the optional server care add-on: operating-system patches, backup checks and monitoring.

More in Trust centre 7 pages

Questions

Questions people ask

Something else on your mind?

A person from our team replies, usually the same day.

Ask a question
01Why not promise 99.9% on every plan?

On the smaller plans the database sits on the same server as everything else, so one bad night can use up a whole month's 99.9% allowance. Only the Large plan has a standby database, so only it targets 99.9%.

02Do you have a public status page?

Not yet. If something affects your system, we tell you directly, on your support ticket and by WhatsApp or e-mail, and we tell you when it is fixed.

03Does the target cover the GST portal?

No. When the GST, e-invoice or e-way bill portals are down, files can still be prepared in MyRecords, but uploads wait for the portal.

Next step

See it on your own numbers.

A live demo on our sample company, with your questions answered by our team. Or ask us for a quote first.

Get a quote

Live demo

Book a walk-through

  • On our sample company, for your kind of work
  • A quote for the modules you need
  • Your questions, answered by our team