Skip to content
VoIPThug — homeBuild My Stack
Hand-inked campaign illustration of a physical signal exchange: one telecom engineer patches a teal fibre run into an unlabelled bay, a second coordinates with an open hand, and a third checks a mechanical failover lever, with copper and fibre spines curving overhead and a rain-dark city beyond a tall window.

The operator

We run the network behind the product

You are dealing with the operator of the platform. Not a brand in front of one, not a partner programme, not a portal skin over somebody else's switch. The edge your phones register against and the software your floor runs on are built and operated by the same people.

  • Named edge hostnames you can resolve and register against
  • Routing policy and failover we own the decision on
  • Account isolation, call records, recordings and monitoring
  • One escalation path, at any hour, to people with switch access
Build My Stack

Footprint

The edge inventory, as it actually is

Every count and every location below is generated from our edge inventory. When we bring an edge up or take one down, this page moves, because there is no number typed into this sentence to go stale.

23 edge nodes across 19 cities in 16 countries

SIP edge nodes
23SIP edge nodes
cities
19cities
countries
16countries

Europe17 nodes

  • Amsterdam
  • Falkenstein
  • Frankfurt
  • Istanbul
  • London
  • Madrid
  • Milan
  • Moscow
  • Paris
  • Tallinn
  • Vienna
  • Warsaw
  • Zürich

North America4 nodes

  • Los Angeles
  • Montréal
  • New York City
  • Washington, D.C. / Northern Virginia

Asia-Pacific2 nodes

  • Singapore
  • Sydney

Architecture

Four layers, and an honest line around each

'We run our own network' is the kind of claim every reseller makes. Here is exactly what we mean by it, layer by layer, including the layer we do not own.

  • Network plane — ours

    The SIP edge: registration, signalling, media handling and the routing policy that decides where a call goes and what happens when the first choice stops behaving. These are our hostnames and our configuration.

  • Product and control plane — ours

    Portal, dialer and campaign engine, supervisor audio, recordings, transcription and QA, billing and the API. One codebase we build, deploy and operate.

  • Observability — ours

    Registration state, call records, recordings, payment state and monitoring. What we can see about your account is largely what you can see about your account.

  • Upstream interconnection — bought and managed

    We buy termination and numbering from upstream carriers, like every operator does. We select them, monitor them, and move traffic off them when they degrade. We do not claim to own their fibre or their facilities, and we do not hand you their excuses either.

Operators

Failover is a decision, not a hope

The interesting question about a voice network is not what it does on a good day. It is what happens in the ninety seconds after an upstream route starts returning nonsense mid-shift.

  • Multiple edges per region

    Regions carry more than one edge where the inventory allows, so losing one is a reroute rather than an outage for everyone registered to it.

  • Routing policy

    Traffic follows policy we control, and we can change that policy for a destination, a carrier or an account without asking anyone's permission.

  • Account isolation

    Accounts are isolated from each other: separate credentials, separate numbers, separate call records, separate recordings. Your neighbour's bad week is not your problem.

  • Monitoring and escalation

    We watch registration, routing and call quality ourselves, and the escalation path ends with people who can change the configuration rather than with a ticket queue.

City reach

Register close to the floor

Pick the endpoint nearest your agents rather than dragging every packet across an ocean and then blaming the internet for the jitter. The full endpoint directory, including which edge your account is provisioned against, is in the portal.

One thing worth being precise about, because it trips up buyers constantly: edge location and local-number availability are separate questions. An edge in a country does not mean we can issue you a local number there, and a local number in a market does not require an edge in that market. When you tell us the markets you are calling, we answer both questions separately.

Questions

Straight answers

Do you own the data centres?
No, and neither does almost anyone making that claim. We operate our SIP edge and our entire product and control stack. We do not own buildings, fibre or every upstream route, and we are not going to pretend otherwise to win a comparison table.
Which edge will my account use?
Whichever is right for where your agents sit and where you are calling. Your provisioned endpoints are shown in the portal with your device credentials, and we will move you if your floor moves.
Is an edge in my country the same as a local number in my country?
No. They are separate. Edge location is about where your phones register and where media is handled; local-number availability is about that country's numbering rules and what documents it requires. Ask us about both and you will get two different answers.
What happens if an upstream carrier degrades?
We move traffic. Carrier selection and routing policy are ours to change, which is the practical difference between an operator and a reseller — a reseller has to wait for the same thing you are waiting for.

Keep reading

Where to go next

The operator

Deal with the people who can change the routing

Send us the markets your floor calls and where your agents sit. You will get a straight answer on the edge you would register against, the numbers we can issue, and the ones that need documents first.

Build My StackWhat we need from you