Open a Support Ticket

How to reach NoBull Networks support through MyNobull, what to include so an engineer can act on the first reply, and where to check network status.

Updated 3 min read

Support at NoBull Networks is handled by engineers, not a script-reading front line, around the clock. The fastest way to reach them is a ticket from MyNobull, and the fastest way to get a useful first reply is to give them what they need to act.

Check status first#

NoBull Networks Status shows platform-wide incidents and scheduled maintenance. If your issue is already posted there, you can save yourself a ticket; if it is not, that is useful information to include.

Open a ticket#

  1. Log in to MyNobull at my.nobullnetworks.com. Tickets opened from your account are automatically tied to your services, which skips the identity back-and-forth.
  2. Choose Support, then Open Ticket, or go straight to submitticket.php. Pick the department that matches your question (technical support, billing, or sales) and select the related service where prompted.
  3. Describe the problem using the checklist below, then submit. Replies land in the ticket and in your email; answering by email is fine.

Not a customer yet, or locked out of your account? Use the contact form and we will get you sorted. Live chat is also available from the website during staffed hours for quick questions.

What to include#

  • Which service: the server name or IP address, or the domain.
  • What you expected and what happened instead, in plain words.
  • When: timestamps with your timezone. "Since about 14:10 Pacific" beats "for a while".
  • The exact error text, copied rather than paraphrased, and how to reproduce it.
  • What changed recently: updates, config edits, new software, a firewall rule.
  • What you have already tried, so we do not send you back through it.
Never put passwords in a ticket

We do not need your root or MyNobull password to help, and we will never ask for it. If we genuinely need temporary access to a server, we will agree a method with you inside the ticket, and you should rotate any credential afterwards.

What to expect#

  • Response times: our first-response target is under 60 minutes, and the recent average is well inside that. Emergencies affecting service availability are triaged first.
  • Language: support is offered in English only.
  • Scope: our services are unmanaged. Anything at the infrastructure layer (hardware, network, power, the virtualization platform, console access) is ours to fix, and we will dig into it. Application-level questions (how to configure your software) are best answered by that project's documentation, though we will happily point you in the right direction.

Common things you can do without a ticket#

Still stuck? Real engineers answer tickets around the clock, and the status page shows anything network-wide before you ask.