Under attack?
Support

You will be talking to a person

Not a policy we advertise - a decision about what this business is. When a network is down, the cost of being misunderstood is measured in minutes, and every layer between you and somebody who can change a rule is one of those minutes spent.

No AI in the loop

Nothing answers before a human does

No chatbot on the site, no AI agent on the first line, no language model reading your ticket and deciding its priority. The first reply you get is written by an engineer who can already see the traffic you are describing.

Direct to engineering

One escalation, not four

The people on the NOC line are the people who operate AS4849 and who wrote the filter. There is no tier one whose job is to ask you to reboot, and no queue between you and somebody who can change a rule.

Under attack

Reachable the way you actually work

Email or a shared channel with your team, 24 hours a day, every day. During an incident we stay with it until the traffic is clean, and you get the packet-level record of what was dropped afterwards.

Why there is no AI anywhere in this

A model answering first is cheap for us and expensive for you. It cannot see your traffic and it cannot change a filter. Its job is to reduce the number of conversations an engineer has - precisely the opposite of what you want at three in the morning with a prefix under attack.

We also think it would be strange to sell a service built on measuring things carefully and then put a system that guesses in front of it. So there is no chatbot on this site, no AI agent on the first line, and no model reading your message and deciding how urgent it is. If that changes we will say so on this page rather than quietly.

Beyond our own network

The same support, on your equipment

Support here does not stop at the services you buy from us. For networks we have designed or built - and for plenty we simply inherited - we hold the operational role end to end.

Watching

Your equipment, monitored 24/7

Client routers, switches and servers sit on the same monitoring the NOC watches our own backbone with - the same screens, the same people, the same night shifts. An interface that starts erroring at 02:40 is being looked at at 02:41, not discovered in a morning report.

Changing

On the line for every change

Configuration changes, maintenance windows, software upgrades, capacity moves - planned with you, executed by us, documented afterwards, with rollback prepared before anything is touched. Routine work is scheduled; urgent work is answered the way an incident is.

How

Brains, not tools that guess

None of this is done with AI tools - not the monitoring triage, not the config changes, not the upgrade plans. What you get is our engineers and more than twenty years of professional system and network administration, applied by hand, with the reasoning written down where you can read it.

One boundary, stated plainly: we support Linux-based operating systems only. Routers, filters, servers, tooling - our entire world is Linux, and twenty years of depth there is exactly why we are useful. We do not work with Windows, and we would rather tell you on this page than surprise you in a scope call.