AS209101 · engineers on shift

Transit, address space and bare metal — one network, one team.

AS209101 is deliberately small and deliberately boring to operate. You talk to the people who own the route policy, hold the filters and rack the machines — not to an account manager reading a script.

5+ TbpsBlended capacity
99.99%Uptime commitment
<1 msInside the backbone
24/7Reachable engineers
UTC --:--:--Z
AS209101 · sessions established
RPKI · origin validation enforced
Route policy · documented and exported
Abuse desk · 24/7 intake
Multi-homed · independently routed
01 — What runs here

Five products. No bundles you didn't ask for.

Everything below is delivered on our own address space, our own filtering and our own hardware — or routed to yours.

01

Transit & interconnection

A blended Tier-1 mix plus direct peering, handed over from 1G to 100G. Your BGP policy stays yours; we document ours.

02

Bare metal

Single- and dual-socket Xeon or EPYC, NVMe as standard, out-of-band access always. Unmanaged by default — that is the point.

03

Address space

IPv4 allocations from /24 upward with the unglamorous parts done properly: LOA, reverse DNS, ROA, geofeed.

04

Attack mitigation

Filtering at the edge for volumetric floods, blackhole-by-community when you need relief in seconds.

05

Cabinets

Your hardware, our power and uplinks. Racked, cabled, photographed and reachable by remote hands.

06

Routing work

New ASN build-outs, policy audits, IRR/ROA cleanup, migrations between providers — quoted as engineering time.

02 — How it is built

A short list of things we refuse to skip

Most network problems are boring problems: missing filters, stale objects, untested failover. We treat them as the job, not the cleanup.

Every session filtered on day one

Bogon and martian prefixes dropped, prefix-length limits enforced, RPKI origin validation applied wherever a ROA exists. It protects our neighbours as much as our customers.

Failover that has been tested

Multi-homed upstreams with BGP failover we exercise, not merely configure. You get the failure behaviour described in writing, including the parts that are ugly.

Numbers you can audit

Ports, commit, burst behaviour, 95th-percentile billing and mitigation limits are stated before you sign. Nothing depends on the word "unlimited".

Change windows you agree to

Planned work is scheduled with notice, and route-affecting changes are announced rather than discovered. Post-incident notes on request.

03 — AS209101

The system behind the products

One autonomous system, run by one team, with a documented peering policy and a public routing footprint you can inspect before you send us a single packet.

AttributeValue
ASNAS209101
RegistryRIPE NCC
OperatorIP Vendetta Inc. · Seychelles IBC No. 245572
Peering stanceOpen where traffic is mutual, objects required
RPKIOrigin validation enabled, ROAs maintained
Abuse intakeabuse@ipvendetta.com · monitored continuously
04 — Peering and presence

Who we exchange traffic with

Public sessions at major exchanges, private interconnects where volume justifies it, and a peering policy short enough to read on one screen:

  • Settlement-free where traffic is reasonably mutual
  • IRR objects and ROAs required for every announced prefix
  • Consistent announcements at every location
  • Prefix-length limits and bogon filtering enforced
  • Maintenance notice before route-affecting work

Bring your ASN, prefixes, preferred exchange and NOC contact — most sessions are live the same week.

05 — Rules of engagement

What we will not carry

A clean network is a commercial asset. Abuse is handled as an operational event with a documented process, not a judgement call made at 3 a.m.

Prohibited

Never, in any location

CSAMMalware & ransomwareDDoS infrastructureSpam & phishingIP spoofingBotnet C&CFraudIllegal traffickingTerror content

Violations end the service immediately and may be referred to the authorities.

Read the full abuse policy →

Process

What happens to a report

Reports land at abuse@ipvendetta.com and are worked against the source evidence — headers, timestamps in UTC, full log lines. We tell customers what was alleged, and we tell reporters what was done.

Valid legal process gets a full, prompt response. Every request is checked for legal sufficiency before anything is disclosed, because a badly-drafted demand should be answered with questions, not a data dump.

abuse@ipvendetta.com →

06 — Fit

Who tends to stay

We are a poor fit for people who want a marketing brochure and a support tier. We are a good fit for these:

ISPs & eyeball networks

Transit that behaves, peering that is worth having, and engineers who answer routing questions competently.

Hosting & platforms

Address space that is not pre-burned, plus metal with real out-of-band access.

Streaming & delivery

Bandwidth profiles that survive an event, and mitigation that keeps working during one.

Privacy-conscious operators

Clients who want their infrastructure handled quietly, lawfully and without being resold down a chain.

07 — Straight answers

Questions we get before signing

Who actually runs this network?

IP Vendetta Inc., a Seychelles company, operates AS209101 with its own small engineering team. We are not a reseller of someone else's platform — the address space, filters and hardware in front of you are ours.

How is capacity delivered?

Ports from 1G to 100G on committed or burstable profiles, multi-homed with tested BGP failover. If a commit will not hold, we will say so before you order rather than after.

Do you hand over control of routing?

No. Announce your own space with your own policy, or let us originate it for you — either way you can see exactly what we filter and why.

What about IPv4 scarcity?

We hold allocations we can lease from /24 upward, reviewed for prior abuse history before they are offered. Ask for the reputation detail, not just the size.

How quickly does anything happen?

Peering sessions usually within a week of mutual agreement. Bare metal on stock platforms is same-day; custom builds are quoted with a real delivery date.

What if something goes badly wrong?

You get a named engineer, a change window and, afterwards, an honest write-up — including what we got wrong. That is the whole reliability programme.

Next step

Tell us the shape of the problem

Ports and commits, address space, racks, or a routing question you want a second opinion on. You get an answer from an engineer, with numbers attached.