Below you will find up-to-date information about our system's current status and the latest incident reports.
Please contact us at support@nezasa.com in case you need further clarification.
TripBuilder
Operational
90 days ago
99.97
% uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
RateHawk scheduled maintenance on March 21st at 23:00 CEST. During this time, booking of travel services will be unavailable. Their service will be unavailable as they will perform necessary updates to the system. The anticipated downtime is for 8 hour. Posted on
Jun 19, 2026 - 08:18 UTC
Resolved -
The issue has been resolved and all our services are back up and running We apologize for any inconvenience this may have caused. Should you want any further details, feel free to contact us anytime.
Sincerely, The Nezasa Operations Team
Jun 19, 10:24 UTC
Identified -
We are currently experiencing issues with the payment provider system Datatrans. We are working on a solution with the highest urgency and will report back to you shortly. We apologize for any inconvenience this may have caused. Sincerely,
Resolved -
This incident has been resolved
Jun 18, 10:28 UTC
Monitoring -
A fix has been implemented and we are currently monitoring the situation. If you are still affected by this issue, please reach out to our support team and we will assist you as soon as possible.
Sincerely, The Nezasa Operations Team
Feb 27, 16:07 UTC
Identified -
We are currently experiencing a service disruption. TripBuilder users may be affected as follows by this issue: Some itineraries are returning a error and are completely inaccessible We have identified the root cause and are actively working on a fix. If you are affected by this issue, please reach out to our support team and we will assist you as soon as possible.
Sincerely, The Nezasa Operations Team
Feb 26, 13:57 UTC