Home / AS209101
Network record

AS209101

Everything you would check before opening a session with us: registry data, policy, object hygiene and where to verify it independently.

Record

Registry and operator data

FieldValue
ASNAS209101
RegistryRIPE NCC
OperatorIP Vendetta Inc. — Seychelles IBC No. 245572
Registered officeVictoria, Mahé, Seychelles
RoleTransit, peering, address space, server delivery
RPKIOrigin validation enabled; ROAs maintained
IRRObjects published for announced space
Abuse contactabuse@ipvendetta.com
Policy

What we need from a peer

  • A registered IRR object or ROA for every prefix you announce
  • Consistent announcements across all common locations
  • A reachable NOC contact that answers
  • Mutual traffic of reasonable balance for settlement-free sessions
  • Prefix-length limits respected (no /25 and longer in the DFZ)
  • Notice before maintenance that affects routes

Send ASN, prefixes, preferred exchange or interconnect point and a NOC contact. You will get a human reply, usually the same working day.

Announcements

What we originate, and how to check it

Our routing footprint is public. These are the independent sources we would use ourselves — no marketing PDF required.

bgp.tools

Live prefix list, upstreams, peer count and visibility for AS209101.

Open bgp.tools →

PeeringDB

Exchange points, facilities, policy and the contact record we actually monitor.

Open PeeringDB →

Route or prefix query

Need a traceroute from our edge, or a check on how a specific prefix is seen? Ask and an engineer runs it.

Ask the NOC →

Operating the network

How incidents are handled

No black boxes: you get a person, a change window and a write-up.

Monitoring

Interfaces, sessions and prefix availability monitored continuously with alerting into the on-shift engineer.

Escalation

Direct line to the people who hold the route policy, not a tier-one script that ends in an email.

Maintenance

Scheduled with notice and agreed windows; route-affecting work is announced before it happens.

Aftermath

Post-incident notes on request: what broke, what we changed, and what is still imperfect.

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.