All Systems Operational

About This Site

This is Rentman's status page, where you can get updates on how our systems are doing. If there are interruptions to service, we will post a note here.

As always, if you are experiencing any issues with Rentman, don't hesitate to get in touch with us at support@rentman.io and we'll get back to you as soon as we can.

Rentman 4G ? Operational
90 days ago
99.91 % uptime
Today
Rentman 3 Operational
90 days ago
99.97 % uptime
Today
Email delivery ? Operational
Outbound Delivery ? Operational
Mailgun API ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
Past Incidents
Apr 23, 2019

No incidents reported today.

Apr 22, 2019

No incidents reported.

Apr 21, 2019

No incidents reported.

Apr 20, 2019

No incidents reported.

Apr 19, 2019

No incidents reported.

Apr 18, 2019

No incidents reported.

Apr 17, 2019
Resolved - This incident has been resolved.
Apr 17, 19:09 CEST
Update - Today at 15:55 CEST we experienced an outage of our servers which lasted until 17:39. The error was caused by a crash of our mySQL systems on all locations. During this outage all Rentman users were unable to access their account.

We have failback servers in place on which we can migrate in the case of an outage of one of our servers. These servers synchronize Rentman data, so that in case of an outage in one we can always migrate to these backup servers. At 16:02 we ordered our hosting provider Amazon to move our operations to these failback servers. Because of an error that Amazon is still investigating, this process was unsuccessful.

Immediately after the incident our Engineering team started investigating the root cause of the mySQL failure together with the Internal Service team of Amazon.

On site engineers from Amazon rebooted our servers, which caused our systems to be back online again at 17:39.

We realize that an outage of our services has a severe impact on our users to perform their daily activities. Any downtime is therefore not acceptable to us. That's why we will continue to investigate the root issue of the failure and what caused the switch to our backup systems to fail.

We will give you an update as soon as we have more information on the incident. Thank you for your patience.
Apr 17, 18:26 CEST
Update - We are continuing to monitor for any further issues.
Apr 17, 17:46 CEST
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 17, 17:45 CEST
Update - Amazon reported: service team was not able to find the reason of the instances in multiple datacenters to be stuck for now, they are moving it to the team that performs hardware reboots
Apr 17, 17:13 CEST
Update - We are continuing to investigate this issue.
Apr 17, 17:10 CEST
Update - Migrating to the failover location failed. We're working closely together with our hosting provider Amazon to resolve the issue.
Apr 17, 16:32 CEST
Update - We found an issue with the servers hosting our database. We're in the process of migrating to our failover datacenter. We hope to be back in 10 minutes
Apr 17, 16:11 CEST
Update - We are continuing to investigate this issue.
Apr 17, 16:07 CEST
Investigating - We are currently investigating this issue.
Apr 17, 15:58 CEST
Apr 16, 2019

No incidents reported.

Apr 15, 2019

No incidents reported.

Apr 14, 2019
Resolved - This incident has been resolved.
Apr 14, 17:10 CEST
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 14, 16:54 CEST
Investigating - We are currently investigating this issue.
Apr 14, 16:53 CEST
Apr 13, 2019

No incidents reported.

Apr 12, 2019

No incidents reported.

Apr 11, 2019

No incidents reported.

Apr 10, 2019

No incidents reported.

Apr 9, 2019

No incidents reported.