Submit a fault report through the portal
Open a ticket with the affected endpoint, the error code from the log, and the time window when the fault appeared. The desk triages by severity, so a clear reproduction path shortens the first response.
Support channels and response windows
Open a ticket with the affected endpoint, the error code from the log, and the time window when the fault appeared. The desk triages by severity, so a clear reproduction path shortens the first response.
When a corporate portal is down or returning 5xx at scale, call +61-2-3508-3976. The on-call engineer picks up within the agreed window and starts tracing the failing service while the ticket is still being filed.
For architecture reviews, load test scheduling, or questions about a previous report, send details to info@defectivewebsite.com. Expect a reply within one business day, with a named engineer attached to the thread.
Critical faults that stop transactions or corrupt data get a 30-minute response window. The fix target is four hours, assuming the defect is isolated to one service and no third-party dependency is blocking the patch.
High-severity issues that degrade performance or affect a subset of users are answered within two hours. The engineering team aims to ship a verified fix by the end of the next business day.
Normal requests, including load test bookings and code review requests, get a first reply within one business day. The fix or deliverable lands within three days unless the scope changes during triage.
Before opening a ticket, check whether your question is already covered in the FAQ. For anything else, the contact page lists the full escalation path.
If a stress test surfaced a structural flaw in your portal, our QA engineers need a direct line to your team. Reach us by phone or email, or drop by the office during business hours. We usually respond within one working day.
Tell us what your backend is struggling with and we will reply with a concrete testing plan, not a sales pitch.