Managua, Nicaragua

Egress from Managua that cannot be announced from anywhere else.

Static IPv4 on addressing assigned by Nicaraguan carriers. It originates inside the carrier’s own aggregate rather than a hosting range — and RPKI is what makes that impossible to reproduce from outside the country.

Egress topology from Managua Managua as the origin point, with links drawn to Mexico City, Miami, Panama City and São Paulo. Mexico City Miami Panama City São Paulo Managua
Measured RTT to each destination is supplied with a test allocation, from mtr rather than estimated.
01 — Service

Carrier addressing, monthly, verified before you commit.

Addressing

Assigned by the carrier

The space is the Nicaraguan operator’s own, delegated to the circuit. It sits inside the carrier aggregate, not inside a hosting range, and we do not run an ASN of our own — which is the whole argument, not a limitation.

Terms

Monthly, no lock-in

Priced per server, per address and per /24. Three figures quoted up front rather than an invitation to get on a call.

Proof first

Test allocation

Classification and reachability get validated on real addressing before any commitment, with the lookups sent to you dated.

02 — The mechanism

Why it is not produced remotely.

An autonomous system number is not bound to a country by the routing protocol. Global operators originate the same ASN from dozens of countries at once. The constraint here is narrower than geography, and considerably harder to work around.

The Nicaraguan carriers operate their ASNs only from inside Nicaragua, and their route origin authorizations (ROAs) pin each prefix to that origin ASN.

Route origin validation of a Nicaraguan prefix An announcement from the Nicaraguan carrier's own ASN is accepted. The same prefix announced from any other ASN is RPKI-invalid and dropped at the transit provider's edge. ANNOUNCED FROM INSIDE NICARAGUA Nicaraguan carrier origin ASN authorised by ROA Validating transit RPKI + IRR prefix lists ACCEPTED propagates globally THE SAME PREFIX, ANNOUNCED FROM ANYWHERE ELSE Any ASN outside NI a rack in Miami, any budget Validating transit RPKI + IRR prefix lists RPKI-INVALID dropped at the edge
Verifiable from any public route collector in about a minute.
Mechanism 01

RPKI

A ROA fixes the originating ASN and the maximum prefix length. An announcement from any other ASN is RPKI-invalid and is discarded by validating networks, which includes most of the transits visible in the propagation graph.

Mechanism 02

IRR filtering

Transit providers build their prefix lists from registered route: objects. With no object binding the prefix to the announcing ASN, the announcement is filtered at the provider edge.

Mechanism 03

Authorization

No serious transit provider accepts a prefix without a letter of authority from the holder. A Nicaraguan carrier has no reason to issue one to a third party.

The barrier is one of ownership and origin validation, not of geography or capital. Nicaraguan addressing has to be bought from a Nicaraguan carrier, on equipment inside the country. A competitor with unlimited resources cannot announce a Nicaraguan carrier’s space from Miami either, because the global routing system rejects it.

03 — Datasheet

What ships with a test allocation.

Serious enquiries arrive with the same list of questions. All of it is answered in writing, before commitment, rather than after a call.

Routing

Origin ASN, the exact prefix, and confirmation that the addressing is carrier-assigned rather than our own.

Classification

Dated lookups from IPinfo, MaxMind and IP2Location.

Capacity

Port speed, committed rate, burst, and whether billing is on the 95th percentile.

Latency

Measured RTT to Miami, Panama City, São Paulo and Mexico City, taken from mtr rather than estimated.

Operations

Power redundancy, maintenance window, remote hands, and response time.

Legal

The operating entity, who receives abuse complaints, and the local regulatory obligations that apply.

Pricing

Per server per month, per address per month, and per /24. Three figures, not an invitation to discuss.

04 — Contact

Reach a person, not a form.

Correspondence is answered in English or Spanish, usually the same day.

sales@istmonetworks.net

Capacity and commercial

noc@istmonetworks.net

Provisioning and incidents

abuse@istmonetworks.net

Acknowledged within one business day

Validate it before you commit.

A test allocation on real addressing, with the classification lookups dated and the routing data in writing.